Site migration is the highest-risk project in SEO. Done carefully, it is invisible to search engines and rankings hold. Done carelessly, it removes a meaningful share of organic revenue overnight and takes months to recover, sometimes incompletely. The most common cause of failure is not incompetence but underestimation: the SEO workstream is scoped as a redirect mapping exercise near the end of the project rather than a parallel discipline running from planning through post-launch monitoring. Knowing realistic hour ranges before you commit protects both your timeline and your traffic.

How AAMAX.CO Manages Migration SEO Without Losing Rankings

At AAMAX.CO, migrations are one of the engagements where our combined capabilities matter most. As a full service digital marketing company providing web development, digital marketing, and SEO services worldwide, we sit on both sides of the project: we understand the engineering constraints and the search consequences. We join at planning rather than at launch, build and validate the redirect architecture, run staging audits before code freeze, and monitor intensively through the stabilization period. Our SEO services for migrations are structured to protect existing organic revenue first and capture improvement opportunities second. If you have a replatform, redesign, or domain change coming, involving us early is dramatically cheaper than involving us afterward.

First, Define What Kind of Migration This Is

Effort scales with how many variables change simultaneously. Migration types, in rough order of increasing risk:

• Protocol or subdomain change: moving to secure protocol or consolidating a subdomain. Lowest complexity, but still requires redirect and canonical work.
• Domain change: URLs move to a new hostname while structure stays the same. Mechanically simple, reputationally risky.
• URL structure change: same domain, new paths. Requires complete mapping of every indexed URL.
• Redesign: same URLs, new templates, content, and markup. Risk sits in content loss, changed internal linking, and performance regressions.
• Replatform: new content management or commerce system, usually changing URLs, templates, and rendering behavior at once.
• Site consolidation or separation: merging multiple properties or splitting one. Highest complexity because authority is being redistributed.

A redesign with unchanged URLs on a small site might be forty hours of SEO work. A replatform and consolidation of a large ecommerce catalog can exceed five hundred.

Hour Ranges by Phase

The estimates below assume an experienced practitioner and are expressed as ranges for a small site of a few hundred URLs, a mid-size site of a few thousand, and a large site of tens of thousands or more.

Discovery and baseline documentation. Crawling the existing site, exporting indexed URLs, pulling ranking and traffic baselines per page, documenting current technical configuration, and identifying the pages that generate the majority of organic value. Small: 8–16 hours. Mid: 20–40. Large: 50–100. This phase is non-negotiable, because without a baseline you cannot detect or diagnose what broke.

Migration planning and requirements. Defining the target URL structure, specifying technical requirements for developers, planning canonical and internationalization handling, agreeing on the launch sequence, and writing the rollback plan. Small: 8–20 hours. Mid: 25–50. Large: 60–120.

Redirect mapping. Usually the single largest line item. Pattern-based rules handle the bulk, but every high-value and irregular URL needs manual verification. Small: 10–25 hours. Mid: 40–100. Large: 120–300, depending on how much of the catalog can be rule-mapped.

Staging validation. Crawling the staging environment, verifying titles, headings, canonical tags, structured data, robots directives, internal linking, rendering of client-side content, and performance. Expect two or three rounds as issues are fixed. Small: 10–20 hours. Mid: 30–60. Large: 80–160.

Launch support. Being present during deployment, verifying redirects in production immediately, confirming robots and sitemap configuration, submitting updated sitemaps, and checking analytics and tag firing. Small: 4–8 hours. Mid: 10–20. Large: 25–50.

Post-launch monitoring and remediation. The phase most often omitted from estimates. Daily checks for the first two weeks, then weekly through the first quarter: indexation, crawl errors, redirect chains, ranking movement against baseline, traffic by template, and performance metrics. Small: 15–30 hours. Mid: 40–80. Large: 100–250.

Totaling these, a small site migration typically runs 55–120 hours, a mid-size site 165–350, and a large or complex migration 435–980 hours or more.

Factors That Push Estimates Higher

Several conditions reliably increase effort, sometimes substantially. Multiple simultaneous changes—new domain, new URLs, new platform, and new content in one release—multiply verification work. International sites with language and region targeting require careful handling and validation across every variant. Ecommerce catalogs with faceted navigation, variant URLs, and pagination create large numbers of edge cases. Client-side rendered applications need rendering verification that server-rendered sites do not. Poor documentation of the legacy site means reverse-engineering current behavior. Content reduction during a redesign, which is extremely common, requires deciding what to preserve, consolidate, or intentionally retire. Legal or compliance review of content adds calendar time and coordination hours.

Where Cutting Hours Causes the Most Damage

When budget pressure arrives, some phases are safer to compress than others. Reducing discovery is the worst choice, because you lose the ability to measure impact or prove what changed. Skipping staging validation guarantees that avoidable errors reach production, where fixing them costs more and traffic is already lost. Truncating post-launch monitoring means problems are discovered by a revenue report rather than a crawl, weeks later.

Safer compressions include limiting manual redirect verification to the pages representing the top share of organic value while relying on patterns for the long tail, and deferring non-critical improvement opportunities to a post-migration optimization phase rather than bundling them into launch.

Practical Estimating Advice

Build your estimate bottom-up from the phases above rather than quoting a single figure. Add a contingency of twenty to thirty percent, because migrations reliably surface unknowns. Express the estimate as a range tied to explicit assumptions about URL count, migration type, and platform, and revise it after discovery when the real scope is visible.

Schedule the launch away from your peak commercial season and avoid Fridays, so issues are found and fixed with a full team available. Freeze unrelated site changes during the stabilization window so that any ranking movement can be attributed confidently.

The Estimate That Actually Matters

The most useful number is not hours but exposure. Calculate what a twenty percent organic traffic loss lasting three months would cost your business. For most companies with meaningful organic revenue, that figure dwarfs the entire migration SEO budget. Framed that way, the question stops being how few hours you can spend and becomes how confidently you can protect what you already have while positioning the new site to perform better than the old one.