Skip to main content

Migrate an Old Site

💡 In this guide, you will check migrated content, unbind the old domain, and point DNS to the new AllinCMS site. Estimated time: 10 minutes.

If you used the old builder before, the new AllinCMS admin can usually use the same account and password. The domain still needs to point to the new site.

Overview

1Open new admin
2Check content
3Unbind old domain
4Copy new CNAME
5Replace DNS

1. Check Content

Log in to the new admin:

https://workspace.laicms.com

Open the migrated site and check:

  • Products are complete.
  • Posts are complete.
  • Media images look normal.
  • Pages can open.

If content is missing or abnormal, record the issue and contact support first. Do not rush to create a new site.

2. Unbind Old

If you want to keep using the original domain, unbind it in the old admin first.

Old admin:

https://website.laifa.xin/workspace

Open Sites -> Admin -> Site Settings, select the old primary domain, disable it, then confirm deletion.

Old builder site entry - the site list opens the admin area used to find domain settings for the old website

Old builder site settings - the page shows domain enabled state and delete entry used to unbind the old domain before migration

3. Get New Record

Return to AllinCMS admin and open the migrated site.

Do not create a new site

If the migrated site already exists, do not create another site. Otherwise you may bind the domain to an empty site.

Open Dashboard -> Domains, then copy the generated CNAME target.

AllinCMS admin migrated site list - the new admin shows the migrated site and dashboard entry, avoiding creating another site

AllinCMS admin domain CNAME record - the domain page shows the generated CNAME target used to replace the old website DNS record

4. Replace DNS

Open your DNS provider, such as Alibaba Cloud or Cloudflare. Find the CNAME record that pointed to the old site, delete it, or replace it with the new AllinCMS admin CNAME target.

DNS changes usually take 10 to 30 minutes. Before they fully take effect, access may appear inconsistent.

💡 Not sure how to fill CNAME? Read DNS Setup.

5. Confirm

  • ✅ Domain verification passes in the new admin.
  • https://www.example.com opens the new site.
  • ✅ The old admin no longer binds this domain.
  • ✅ Products, posts, and pages match the new admin.

Pitfalls

MistakeResultHow to avoid it
🔴 Creating a new site for migrated contentDomain may bind to the wrong siteUse the migrated site
🔴 Old admin still binds the domainDomain conflictUnbind old domain first
🟡 Judging right after DNS changeFalse failureWait 10 to 30 minutes
🔴 Deleting email recordsEmail may failDo not delete MX or TXT blindly

Next

📌 Launch Checklist - run the full frontend check after switching the domain.