How to Schedule a Content Freeze So Nothing Gets Lost Mid-Migration
Short Answer
A content freeze stops routine edits on the old site while content moves to the new one. Set its scope and dates, route urgent changes through one approver and exception log, then reconcile before cutover.
Two weeks after a new website launches, someone notices that last month's price change never made it across. The marketing team updated the old site shortly after the content export ran. Nobody logged the change, so nobody moved it across. The new site went live with outdated information, and the old version with the correct price is now gone for good.
A properly planned content freeze prevents exactly that. It is a short, agreed period when routine edits on the old site stop, so the content being migrated stays stable. This guide explains how to set the scope and dates, handle urgent changes and reconcile edits before cutover. It also covers reopening publishing without creating a second round of confusion.
What exactly should a content freeze cover?
A content freeze covers every piece of content that will be moved to the new site. That includes pages, blog posts, products, prices, images, menus and downloadable files. It pauses routine editing on the old site, but not enquiries or online orders.
Write the scope down clearly, including what is not frozen, such as incoming form submissions and customer accounts. Name the systems involved, like the content management system, product feed, booking tool or CRM. Without a written scope, teams guess, and those guesses create gaps in the new site.
Quick Answer
A website migration content freeze pauses routine edits to pages, posts, products, prices and media being moved. Enquiries, orders and form submissions continue normally, and the scope belongs in writing.
How long should a content freeze last?
Keep the freeze as short as the migration allows, usually from the final content export until the new site is live and checked. Work backwards from the planned launch date to find the export date. Mark both dates on a shared calendar that every editor can see.
Allow time for importing, checking redirects and testing forms before cutover. Freezes that stretch across several weeks tempt teams to make quiet edits, which defeats the whole purpose of freezing. If the launch date slips, agree formally whether the freeze continues or pauses.
Quick Answer
A content freeze should run from the final export until the new site is live and verified. Keep it short, and agree formally what happens if the launch date slips.
How should urgent changes be handled during the freeze?
Route every urgent change through one named approver, who decides whether it truly cannot wait. Approved changes go into an exception log recording the page, the change, who made it and when. That log becomes the reconciliation checklist for the new site before launch.
Do not let urgent requests travel through private chats or phone calls alone, because they vanish from the record. Legal corrections, safety information and genuinely wrong prices are sensible exceptions to the rule. A new promotional banner or blog post can usually wait until after launch.
Quick Answer
During a content freeze, send urgent changes through one named approver and record each in an exception log. Keep requests out of private chats, where they are easily lost later.
How do you reconcile edits made after the export?
Before cutover, compare the old site against the export for every page and product in scope. Use the exception log first, then check modification dates, sitemaps and a crawl of both sites. Timestamps alone can miss changes to menus, widgets or site settings.
Apply each confirmed change to the new site, then tick it off the log with a date. Pay extra attention to prices, contact details and legal pages, since errors there cause the most customer harm. Bilingual sites need the Arabic and English versions checked fully separately too.
Quick Answer
Reconcile before cutover by working through the exception log, then comparing modification dates, sitemaps and crawls of both sites. Check prices, contact details, legal pages and each language version separately.
How do you reopen publishing after launch?
Reopen publishing only on the new site, once redirects, forms, tracking and key pages have passed their checks. Remove or restrict editing access on the old site at the same time. Otherwise someone will eventually update the wrong system out of habit.
Google Search Central recommends keeping redirects from old URLs for as long as possible, generally at least a year. Keep the old site available privately, in read-only form, for reference during that period. Tell every editor and agency, in writing, where content now lives and who approves it.
Quick Answer
Reopen publishing on the new site only after redirects, forms and key pages pass checks. Restrict editing on the old site, and keep old redirects for at least a year.
Main Takeaways
A website content freeze pauses routine edits on migrated content while enquiries and orders continue. Keep it as short as possible, running from final export to verified launch. Route urgent changes through one named approver and a written exception log. Reconcile every logged change before cutover, then reopen publishing only on the new site and keep redirects for a year.
Planning your freeze before the migration starts
A content freeze is a small piece of planning that prevents an awkward and expensive launch. The work is mostly organisational: a written scope, one approver, one log and a clear reopening date. None of it needs special software or extra budget. It just needs to be agreed by everyone before the final export runs.
For the wider picture, our website migration checklist for UAE businesses covers redirects, testing and launch steps. If many people must sign off pages, the guide to staging approval workflows helps keep reviews moving. Auronix Web Studio's website development team can plan your migration with a documented freeze and reconciliation step. Set your freeze dates at the same meeting where you fix the launch date.
Sources & References
FAQs
Questions readers usually ask next
These FAQs are written to match the topic of this post and to help readers move from understanding to action.
Does a content freeze stop enquiries and orders?
No, a content freeze only pauses editing of migrated content. Enquiries, orders, bookings and form submissions continue exactly as normal, though they may need exporting separately before the final cutover.
Who should approve changes during a content freeze?
One named person with clear authority over the website content should approve every single change. A single approver avoids conflicting instructions and keeps the exception log accurate and complete throughout.
What should an exception log record?
Record the page or item, the change, the reason, who approved it, who made it and the date. That detail lets the team repeat each change on the new site.
Are modification timestamps enough to find changed content?
No, timestamps can miss changes to menus, widgets, settings or files replaced directly on the server. Combine them with the exception log and a crawl comparison of the two sites.
How do scheduled blog posts affect a content freeze?
Scheduled posts can publish during the freeze and be missed by the export. Pause them, or list them in the exception log so they are recreated on the new site.
Should the final import overwrite everything on the new site?
Only if no editing has happened on the new site since the previous import. Otherwise, apply the changes selectively, so later work on the new site is not overwritten accidentally.
Do bilingual websites need a separate freeze check?
Yes, because Arabic and English versions are often edited by different people at different times. Reconcile each language version separately, and confirm right-to-left layouts on mobile after importing late changes.
When should editing access on the old site be removed?
Remove or restrict it at cutover, once the new site is live and fully checked. Keep a private read-only copy available for reference while redirects and Google search results settle.
What is a useful migration rehearsal?
Migrate a small sample of real pages, products and forms to staging before the full move. The rehearsal reveals export gaps, formatting problems and missing redirects while there is time.
Should customers be told about a content freeze?
Usually not, because customers should notice nothing while enquiries, bookings and orders continue normally. Internal teams, agencies and anyone else who edits content must all be told clearly and early.
Related Resources
Need help choosing the right stack?
We help UAE businesses keep public pages fast, indexable, and conversion-friendly, then reserve heavier frameworks for the parts that actually need them.
Built for search-ready UAE websites that need clarity, speed, and trust.
