Foundation · 2 min
What you need to know
How should ecommerce pages be migrated?
Inventory every page and map its title, body, media, metadata, template and URL to the destination. Review rendered output because a successful content import can still produce broken layouts.
How should blog content be migrated?
Transfer posts with authorship, dates, categories, media, metadata, and internal links. Preserve valuable URLs where possible and map changed URLs to the closest equivalent post.
Should old blog posts be migrated?
Migrate posts that retain customer, search, reference or brand value. Consolidate or archive obsolete and conflicting posts through an intentional content and URL decision.
How should metadata be preserved?
Map title tags, meta descriptions, headings, social metadata, and other required fields separately from body content. Confirm the new templates do not overwrite page-specific values.
How should internal links be updated?
Rewrite owned links to their final destination URLs and update embedded assets at the same time. Do not leave internal navigation dependent on redirects.
How do I detect broken content after migration?
Crawl the release candidate for missing pages, broken links and assets, empty fields, and redirecting internal links. Add visual checks for templates, embedded content, and responsive layouts.
A quick store check
Crawl one content type, then visually inspect a representative page for missing fields, broken embeds, incorrect templates and redirected links.
Foundation · 2 min
Frequently asked questions
Should obsolete content be redirected automatically?
Only to a genuinely relevant replacement. Otherwise, consolidate, archive, or return an appropriate removal response.
Can content rewriting happen during migration?
Yes, but track it as an approved content change with separate review and URL decisions.