CorefinityCorefinityDocs
Open the Control PanelControl Panel
Migrate to Corefinity · 4 of 7

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

  1. The assistant reads the old site and changes nothing there.
  2. It checks the versions against what Corefinity supports.
  3. 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.
  4. It holds the copy, so it cannot act as the live site: Scheduled tasks off, queues held, no sending domain.
  5. It copies the files and imports the database. A backup is taken before each import.
  6. 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

WayWhat happens
rewrite-urlsThe copy's addresses point at the site's platform address. The final copy brings the real addresses back, then the domain is attached.
pending-dnsThe 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.

  1. The old site goes into maintenance and its crontab is commented out. Nothing on the old server is stopped or deleted.
  2. You stop the old host's queue workers when asked. If they cannot be stopped, the switch ends here and the old site reopens.
  3. The latest files and database are copied across.
  4. DNS moves: through Cloudflare when it is connected, otherwise you change the records.
  5. The holds come off in order: email first, then queues, then scheduled tasks.
  6. The live domain is tested, and the logs are read for errors.

Roll back

WhenWhat it takes
Before DNS movedThe 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 movedThe 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.

Text
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.
Was this helpful?
Open in ClaudeOpen in ChatGPT