Documentation Index
Fetch the complete documentation index at: https://learn.nexudus.com/llms.txt
Use this file to discover all available pages before exploring further.
Step-by-step Migration
This page covers every technical step involved in moving from version 4 (or earlier) to version 5 of the Members Portal.Step 1 — Preview the new portal
Before making any changes, you can preview exactly what your customers will see on version 5.Find your portal domain
Open Settings > Website > Domain in your Nexudus dashboard. Note the value in the Domain field — for example,
kalkio.Open the preview URL
Append This is a live preview of your portal running on version 5 with your current data and configuration.
.nexudus.site to your domain value and open it in your browser. For example, if your domain is kalkio, open:Walk through the portal
Sign in with your own credentials and explore the key areas:
- Dashboard — check that announcements, bookings, and quick actions display correctly
- Resources — verify that rooms, desks, and other resources appear with the right names, images, and pricing
- Events and courses — confirm that upcoming events display correctly
- Profile and billing — review that invoices, payment methods, and personal details are accurate
- Team management — if you use teams, verify the team section
Step 2 — Customise the portal
Before going live, take the opportunity to adjust the portal to match your branding and preferences.Page editor
The new drag-and-drop page editor lets you customise every page visually — rearrange sections, add components, show or hide content for different audiences, and create entirely new pages. Access it athttps://your-portal-url/admin/editor while signed in as an operator.
Custom code
If you use custom CSS, JavaScript, or head elements in your current portal, these continue to work in version 5 through the Web Template Editor.Step 3 — Update DNS (custom domains only)
If you use a custom domain for your portal (e.g.,members.yourcompany.com), you need to update your DNS records and issue new SSL certificates after migrating.
Open domain settings
Go to Settings > Website > Appearance and locate the DNS configuration section.
Remove old DNS records
In your DNS provider, remove any A or CNAME records that currently point to
spaces.nexudus.com.Add new DNS records
Add the new DNS records displayed in the domain settings page. These typically include:
| Record type | Name / Host | Value |
|---|---|---|
| CNAME | Your subdomain (e.g., members) | Value provided in the dashboard |
| A | @ or your apex domain | IP address provided in the dashboard |
Issue new SSL certificates
Follow the instructions on the domain settings page to issue new SSL certificates for your custom domain. The system handles certificate generation automatically once your DNS records are verified.
Step 4 — Go live
When you are ready to switch:Open the portal settings
Navigate to Settings > Website > Domain in your Nexudus dashboard.
You can roll back to the previous version at any time from the same settings page. See Rollback and troubleshooting for details.
What happens to old links and URLs
After going live:- Old links are redirected automatically. Any links previously distributed to customers — in emails, bookmarks, documents, or notifications — that pointed to the old portal will automatically redirect to the corresponding page on the new version. No action is required from you or your customers.
- Old default domain redirects to the new one. If you are not using a custom domain, anyone accessing the old address (ending in
.spaces.nexudus.com) will be automatically redirected to the new one (ending in.nexudus.site).
Step 5 — Verify everything
After going live, run through this checklist:- Portal loads correctly at your primary URL
- Customers can sign in with existing credentials
- Dashboard displays upcoming bookings and announcements
- Resource booking flow works end to end
- Invoices and payment history are visible
- Custom CSS and JavaScript are applied
- Email notification links point to the new portal
- Custom domain resolves correctly (if applicable)
Next steps
Communicating with customers
Suggested timeline and guidance for keeping members informed.
Rollback and troubleshooting
How to revert to the previous version and resolve common issues.