Content modelling
Migrate a CMS without a content freeze
The BetterCMS team Engineering
Share this post
Summarize with
AI
TL;DR, key takeaways
- Move in slices, so most of the site keeps publishing while one section migrates.
- The content mapping is where the real work of a migration is.
- Every changed URL needs a redirect before cutover, not after.
- Verify each slice while the old system is still standing.
Every replatform plan contains a sentence like "content freeze from the 3rd". It is there because the team cannot keep two systems in agreement while both are being edited, so they stop editing one of them.
Freezes are costly in a way that does not appear on the project plan. Campaigns slip, fixes queue up, and the pressure to unfreeze early is what turns a careful cutover into a rushed one. The way out is to never need both systems to agree about everything at once.
Move in slices, not in one cutover
A slice is a set of pages that share a template and an owner. The blog is a slice. The docs are a slice. The nine legal pages nobody has touched since 2023 are a slice, and a good first one.
Each slice moves on its own schedule. While a slice is moving, its pages are frozen and the rest of the site is not, so the freeze is measured in days on a subset rather than in weeks on everything.
- Inventory the slice. Every URL, its template and who edits it.
- Map the old fields to the new model, and write down what has no home.
- Import into drafts and review them without publishing anything.
- Point the routes at the new system and redirect any URL that changed.
- Verify, then remove the old template so nobody edits a dead page.
The mapping is where the work is
Imports fail on the fields that do not correspond. An old system stores a body as one HTML blob, and the new model has a structured body. An old system has three date fields and the new one has two. Those decisions are not technical and they should not be made by whoever runs the script.
Write the mapping as a table before any code runs. Old field, new field, transform, and a decision for the ones with no target: drop, merge or keep in a holding field for later. A holding field is not defeat. It is a way to move without losing anything you cannot get back.
What breaks when a URL changes?
Links break, rankings drop and every bookmark a customer saved stops working. Most of it is preventable with redirects, and redirects are cheap to write and expensive to remember later.
Build the redirect map from the inventory in step one, at the same time as the field mapping. Any URL that is not identical in the new system gets a permanent redirect, and the list is verified as part of the slice rather than after launch.
Verify with the old system still standing
Keep the previous CMS readable until the last slice has been live for a month. Not editable, readable. It costs almost nothing and it is the difference between a missing image being an annoyance and being gone.
A migration is finished when nobody can edit the old system, not when the new one is live.
The last step of every slice is removing the old edit path. A migration that leaves two places to publish has not reduced anything, and within a quarter somebody will have used the wrong one.
Your next website starts here
See BetterCMS running on your pages, not on a sample site.