To scope a site migration timeline, break the move into inventory, build, content transfer, testing, and launch. A site migration is any change that moves URLs, platforms, hosts, or site structure in a way that can break links, forms, and tracking.
Assign hours and owners to each part before you set a launch date. Most delays come from unclear content decisions and missed redirects, not coding. A clear scope lets marketing, development, and content teams agree on what moves, what gets cut, and what must work on day one.
Table of Contents
- What counts as migration scope?
- How do you map content and redirects?
- How long should each phase take?
- How do you protect traffic and leads?
- What belongs in launch week?
What counts as migration scope?
List every item that can change behavior for visitors. That includes pages, posts, media files, navigation, forms, checkout steps, logins, site search, feeds, and integrations for email, analytics, and ads. Note the source and destination for each, such as WordPress to Drupal, old theme to new theme, or old host to new host. Separate must-carry items from nice-to-have improvements.
A contact form, donation flow, or top service pages must work at launch. A new blog layout or extra landing pages can wait until after launch if time runs short. Record who approves content, design, and technical work. Migration stalls when no one can say yes to deleting old pages, merging duplicates, or freezing edits during the move.
How do you map content and redirects?
Crawl the current site and export a full URL list with titles, traffic, links, and conversions. Match each old URL to one new destination, a planned rewrite, or a deliberate removal. Pay special attention to pages with many inbound links, paid-ad destinations, and high-value lead forms. Build the redirect map early, not during launch week.
For example, /services/web-design/ should point to its exact replacement, not the homepage. Broad catch-all redirects confuse visitors and hide broken paths from reports. Lock content edits once mapping starts. If editors keep adding pages or changing slugs, the map goes stale and testing fails. Set one cutoff date for new content and one owner for exceptions.
How long should each phase take?
Size the timeline from tasks, not from a target date. Count pages for transfer and review, URLs for redirects, templates for front-end build, and systems for testing. Then add time for feedback rounds, fixes, and a calm launch window.
Use these blocks to draft the schedule: Add buffer where unknowns cluster. Custom modules, membership rules, multilingual content, and large media libraries often take longer than expected. A short content freeze also shortens testing because the target stops moving.
- Inventory and redirect map: page list, content decisions, and URL pairs
- Build and transfer: templates, content entry, forms, tracking, and integrations
- Quality checks: links, speed, mobile layout, accessibility, checkout, and lead flow
- Launch and watch: DNS or domain switch, redirect test, sitemap submit, and rank and lead check
How do you protect traffic and leads?
Keep page titles, headings, and core copy stable unless a rewrite is part of the plan. Keep the same URL slugs where possible, and use permanent redirects only for URLs that truly change. Update internal links to point directly to new addresses instead of leaning on redirects. Preserve measurement and paid campaigns.
Recreate conversion events, test each form with a real submission, and check ad landing pages for speed, message match, and tracking. A form that looks fine but sends no notice will cost leads fast. Run a pre-launch check on staging with real content. Click key paths as a visitor would: find a service, submit a form, complete a purchase, and use site search on a phone. Fix blocking errors before launch, and keep minor polish for a punch list after.
What belongs in launch week?
Choose a low-traffic window and assign one decision maker for go or rollback. Publish the step order: backup, put up maintenance mode if needed, push code, switch DNS or domain settings, test redirects, check forms and checkout, and submit updated sitemaps. Keep support staff ready to answer visitor reports.
Watch behavior for several days after launch. Check crawl errors, redirect chains, missing images, slow templates, form notices, purchase alerts, and ad approvals. Fix traffic and revenue risks first, then move to design tweaks.
You Might Also Like
- WordPress Maintenance: Google Sign-In Error Messages: How to Help Users Distinguish Site Problems From Account Problems
- WordPress Maintenance: Data Export vs. a Full Site Backup: Which Files and Settings Does Recovery Require?
- CMS Migration and Web Development Explained for 2026: Who It Affects, Key Evidence, and What to Do Next
