Cut over and roll back
Follow the course every migration with an AI assistant takes, switch the domain to Corefinity in a short window, and go back if you need to.
On this page
Before you start
- An AI assistant is connected to your organisation: see Connect an AI assistant. Its token must last until the move ends: running copies stop when it expires or is revoked.
- The assistant has an SSH login on the old server, such as
ssh [email protected]. Never give it a password.
What every migration does
- The assistant reads the old site and changes nothing there.
- It checks the versions against what Corefinity supports.
- It creates the site, or uses the one you name. A site that deploys from Git is set to manual in Deployment mode until you set it back.
- It holds the copy, so it cannot act as the live site: Scheduled tasks off, queues held, no sending domain.
- It copies the files and imports the database. A backup is taken before each import.
- It tests the copy's pages.
It asks before every change to production, and you choose which of the old server's scheduled jobs to carry over.
Test before DNS moves
| Way | What happens |
|---|---|
rewrite-urls | The copy's addresses point at the site's platform address. The final copy brings the real addresses back, then the domain is attached. |
pending-dns | The domain is attached before DNS points at the site, so tests name the real domain. You add a TXT record for each name to prove it is yours. |
Switch the domain
Run the whole migration once as a trial: its timings are the length of the switch. Lower the domain's DNS TTL to 300 seconds, at least one old TTL ahead.
- The old site goes into maintenance and its crontab is commented out. Nothing on the old server is stopped or deleted.
- You stop the old host's queue workers when asked. If they cannot be stopped, the switch ends here and the old site reopens.
- The latest files and database are copied across.
- DNS moves: through Cloudflare when it is connected, otherwise you change the records.
- The holds come off in order: email first, then queues, then scheduled tasks.
- The live domain is tested, and the logs are read for errors.
Roll back
| When | What it takes |
|---|---|
| Before DNS moved | The old site leaves maintenance, its crontab is put back and you start its queue workers. The copy keeps its holds for another try. |
| After DNS moved | The new site stops answering visitors, DNS goes back, and what it took since the switch is copied to the old host before that reopens. |
Keep the old host until you no longer need the way back.
Start the switch
Name the site, the domain and the way you tested, for the cutover-and-rollback playbook.
Use the Corefinity MCP prompt "cutover-and-rollback" with site: shop.example.com,
domain: shop.example.com, strategy: pending-dns.
Follow it step by step and tell me before anything that changes my account.Related
Was this helpful?