Reset page cache, object cache, CDN cache, and browser cache rules after a CMS migration. A CMS migration moves pages, media, URLs, and templates from one content management system to another. Old cache stores copies of the previous site structure. If you keep it, visitors may see broken layouts, missing images, or old redirects.
Official resources:
- Purge all Cloudflare CDN cache after migration — Clear stale CDN content so new CMS pages serve fresh from origin.
- Reset HTTP Cache-Control headers correctly — Verify browser caching rules so migrated pages revalidate properly.
Table of Contents
- Why does old cache cause problems?
- Which site caches should you clear first?
- How do you reset CDN and DNS-level cache?
- What about browser cache and file headers?
- How do you handle forms, carts, and logins?
- Frequently Asked Questions
Why does old cache cause problems?
Cached files point to old paths, theme assets, and database queries. After migration, those paths and queries often change. The result is mixed content, blank blocks, or checkout and search errors.
Stale cache also hides migration mistakes. Editors may see a correct page while visitors see an old one. Purge everything early so you test the live site, not a copy.
Which site caches should you clear first?
Start with the application caches inside the new CMS. That usually means page cache, object cache, and any migration or import cache.
Disable aggressive caching until content and redirects test clean. Re-enable it layer by layer.
- Flush page cache so full HTML pages rebuild from new templates.
- Flush object or database cache so menus, widgets, and queries rebuild.
- Clear transients, render cache, or Twig cache if your CMS provides them.
- Reset cache plugins or modules to default exclusions, then reconfigure them.
How do you reset CDN and DNS-level cache?
Purge the CDN cache for all changed URLs, or purge everything for a full rebuild. Update CDN rules that minify files, rewrite URLs, or serve stale content on origin errors.
Check DNS and edge settings carried over from the old host. Remove old page rules, workers, and edge redirects that conflict with the new CMS. Confirm the CDN pulls from the new origin and respects new cache headers.
What about browser cache and file headers?
Set fresh cache headers for CSS, JavaScript, images, and fonts. Use versioned filenames or query strings so browsers fetch new assets instead of old ones.
Review settings for cache lifetime, ETags, and compression. Shorten lifetimes during launch week, then lengthen them once pages stabilize. Test in a private window to see what a new visitor receives.
How do you handle forms, carts, and logins?
Exclude interactive pages from page cache. That includes login, account, cart, checkout, search, and contact forms.
Confirm user roles and permissions bypass cache correctly. Submit a test form, log in as a test user, and add an item to the cart. If private data appears for another visitor, tighten cache exclusions before launch.
Frequently Asked Questions
Should you keep old cache to speed up launch?
No. Purge all caches at launch, then let them rebuild from the new CMS.
How long should you use short cache times?
Keep times short until URLs, templates, and redirects test clean across devices, then restore normal values.
Why do images break after cache is cleared?
File paths often change during migration. Update media URLs and resave affected pages, then purge again.
