BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
Cost of Changing a Domain on an Established Site: The Total-Cost Framework Most Migration Guides Leave Out
Ask what it costs to change the domain on an established site, and the answer you get back is a development quote: three or four thousand dollars to move the files and set up redirects. That number is real, and it is also the smallest part of the bill.
The true cost of a domain change has four parts, and only one of them ever shows up on an invoice. There are the direct costs you pay a freelancer or agency. There are the indirect costs in your own team’s hours. There is the opportunity cost of the organic revenue you give up while rankings recover. And there is the risk cost on the share of migrations that never fully come back. This guide prices all four, against cited figures, so the real budget is visible before the work starts.
One lever cuts the largest line item, and the field ignores it. The destination domain decides how steep the recovery curve is. Move onto a fresh registration and authority restarts from zero. Move onto an aged domain that already carries relevant authority and the inherited equity offsets the dip. SEO Domains operates the curated marketplace where that destination raw material is screened before it is priced.
What changing domains actually costs an established site
For an established site, a domain change runs from roughly 1,500 US dollars for a small brochure site to 20,000 dollars or more for a content-heavy or ecommerce property, before any lost revenue is counted. Once the recovery window is priced in, the opportunity cost frequently exceeds the entire build invoice. The total is four costs stacked together, not one.
The published cost guides agree on the visible range. Webyking, CMSMinds, and Cloudways, three 2026 website-migration cost guides, put a sub-50-page site between 1,500 and 5,000 dollars, a mid-sized site between 5,000 and 20,000, and an enterprise or ecommerce migration anywhere from 20,000 to 250,000 dollars. Those are the direct numbers, and they are the part the field prices well.
What the field underprices is everything that does not arrive as a line item. A site that already ranks has equity to protect, and a domain change puts that equity through a recovery window where traffic drops before it returns. The cost of that window, the cost of your own team’s time, and the cost on the fraction of changes that never recover are the three buckets this guide adds. The starting decision behind all of them is covered in When to migrate from an old domain.
The four cost buckets: direct, indirect, opportunity, risk
Every dollar a domain change costs falls into one of four buckets. Direct cost is what you pay other people. Indirect cost is what your own team spends. Opportunity cost is the organic revenue forgone while rankings recover. Risk cost is the probability-weighted permanent loss on changes that never return. The published guides price the first bucket and leave the other three implicit.
Separating the four matters because they scale differently. Direct cost scales with site size and platform complexity. Opportunity cost scales with how much organic revenue the site earns and how long recovery takes. A small site with a large organic revenue base can have a trivial direct cost and a punishing opportunity cost, and a budget built on the invoice alone will miss it entirely.
1. Direct cost (the invoice)
What you pay outside the business: migration build, redirect mapping, theme rebuild, the destination domain itself, SSL, email migration. This is the number the field quotes.
2. Indirect cost (your hours)
Internal time: planning, QA, content review, customer communication, updating every asset that names the old domain. Real money, never invoiced.
3. Opportunity cost (the recovery window)
Organic revenue given up while traffic dips and returns. Computed as monthly organic revenue times traffic-loss percentage times recovery months. Usually the largest of the four.
4. Risk cost (the tail)
The probability-weighted permanent loss on the share of migrations that never fully recover. Priced from cited recovery-failure rates, not assumed away.
Direct costs, itemised
The direct cost of a domain change splits into predictable line items: the destination domain, the migration build, redirect mapping, theme or template rebuild, SSL and security, email migration, and post-launch monitoring. Across the published 2026 guides, planning runs 10 to 20 percent of the build, content and data transfer 20 to 30 percent, redirect setup 5 to 10 percent, and post-migration validation 15 to 25 percent.
These percentages come from the CMSMinds and Cloudways 2026 cost breakdowns, which split the build into pre-migration, execution, and post-migration stages. The execution stage is the bulk of the budget. The pre and post stages are where teams under-budget, because audit and validation feel optional until a broken redirect costs a week of traffic.
| Direct line item | What it covers | Typical share or figure |
|---|---|---|
| Destination domain | New registration, or acquisition of an aged domain with existing authority | 10 to 50 USD/year new; aged domains priced on their authority profile |
| Planning and audit | URL inventory, redirect map, technical pre-flight | 10 to 20% of build (CMSMinds) |
| Content and data transfer | Moving pages, database, media to the new domain | 20 to 30% of build (CMSMinds) |
| Redirect mapping and setup | 301 redirect for every old URL to its new equivalent | 5 to 10% of build (CMSMinds) |
| Theme or template rebuild | Design carried or rebuilt on the new domain | 1,000 to 15,000 USD (Webyking) |
| SSL, email, integrations | Certificate, mailboxes, third-party reconnections | SSL low; email 2 to 5 USD/mailbox (Cloudways) |
| Post-migration monitoring | Validation, error tracking, GSC submission | 15 to 25% of build (Cloudways) |
| Old-domain renewal | Keeping redirects alive on the old domain | 10 to 15 USD/year, hold at least 1 year |
The single line item the field treats as an afterthought is the destination domain. A new registration costs 10 to 50 dollars a year. An aged domain that already carries relevant, earned authority is priced on its backlink profile, and that price buys a shorter recovery window. The redirect mechanics that protect equity once the domain is chosen live in Building the 301 mapping sheet.
Indirect costs: the work no invoice shows
Indirect cost is your own team’s time, and it rivals the build invoice on a site of any complexity. It covers planning hours, QA, content review, customer communication, and the unglamorous work of updating every asset that still names the old domain: email signatures, social profiles, ad accounts, printed material, and partner listings.
This bucket is invisible because nobody sends a bill for it. A marketing manager who spends three weeks coordinating a migration has spent real salary, and that salary is part of the cost of the change. Cloudways notes that handling SEO preservation separately can double a migration budget, and the bulk of that doubling is labour, internal or contracted.
The asset-update work is the part teams forget until launch day. Every place the old domain appears is a place a customer or a crawler can hit a dead end. The technical side of that checklist is documented in Migration technical checklist, and the customer-facing side is its own line of hours.
Opportunity cost: the revenue you lose while rankings recover
Opportunity cost is the organic revenue an established site gives up during the recovery window, and for a site that earns from search it is usually the largest of the four buckets. The formula is direct: monthly organic revenue times the traffic-loss percentage times the number of months until recovery. The field discusses traffic drops but stops short of turning them into a dollar figure.
The inputs are cited, not invented. DreamHost reports that the average domain migration takes 523 days to recover, with an early dip in the first two to four weeks and gradual recovery over six months and beyond. Bluehost and HawkSEM both put typical recovery at three to six months for a well-executed change. Traffic loss during the dip is commonly cited in the 30 to 70 percent range across the migration-cost field.
| Input | Worked example | Source of the input |
|---|---|---|
| Monthly organic revenue | 20,000 USD | Your own analytics |
| Average traffic loss during recovery | 40% | Field range 30 to 70% (2026 cost guides) |
| Months to recovery | 6 months | Bluehost, HawkSEM (3 to 6 months) |
| Opportunity cost (revenue forgone) | 20,000 x 0.40 x 6 = 48,000 USD | Computed |
| Compare: a mid-site direct build | 5,000 to 20,000 USD | CMSMinds, Cloudways, Webyking |
The full month-by-month shape of the dip, and the levers that flatten it, are mapped in Expected traffic loss during migration and recovery. The headline is that opportunity cost is the line a budget cannot afford to omit.
Risk cost: when a domain change does not fully recover
Risk cost is the probability-weighted permanent loss on the share of migrations that never return to their original traffic. DreamHost reports that 42 percent of migrations do not fully recover their original traffic, and 17 percent never recover even after 1,000 days. That tail is a real cost, and pricing it means multiplying the permanent revenue loss by its probability instead of assuming a clean recovery.
A clean recovery is the planning assumption every budget makes and the data does not support. If 42 percent of changes fall short of full recovery, then a fraction of the pre-migration organic revenue is at permanent risk on any single migration. On a site earning 20,000 dollars a month, even a modest permanent shortfall compounds into a meaningful annual figure once it is weighted by the failure rate.
What drives the risk up
Incomplete redirect maps, redirect chains, a destination domain with no relevant authority, launching during peak season, and skipping staging. Each raises the chance of landing in the 42 percent that fall short.
What pulls the risk down
A complete one-to-one redirect map, a destination domain that already carries relevant earned authority, low-season timing, staging validation, and the Search Console change-of-address signal.
The mitigations are not separate from the rest of the budget. A clean redirect map and a strong destination domain reduce both the opportunity-cost window and the risk-cost tail at once. The Search Console signal that helps Google process the move is covered in Using GSC’s Change of Address tool.
Total cost by site size
Total cost scales with site size on the direct bucket and with organic revenue on the opportunity bucket. A small brochure site runs 1,500 to 5,000 dollars direct with low opportunity cost. A mid-sized content site runs 5,000 to 20,000 direct, and its opportunity cost can exceed the build. A large ecommerce or enterprise property runs 20,000 to 250,000 direct, with an opportunity cost measured in six figures.
The direct ranges below are the consensus of the Webyking, CMSMinds, and Cloudways 2026 guides. The opportunity-cost column is the addition the field omits, scaled from the worked example in the opportunity-cost section. The point is that the two columns do not move together: a small site with a strong organic revenue base sits in the bottom direct tier and a much higher total tier.
| Site size | Direct build (cited) | Opportunity cost (added) | What dominates the total |
|---|---|---|---|
| Small brochure (under 50 pages) | 1,500 to 5,000 USD | Low if organic revenue is low | Direct build |
| Mid content site (50 to 500 pages) | 5,000 to 20,000 USD | Frequently exceeds the build | Opportunity cost |
| Large ecommerce (500+ pages) | 10,000 to 50,000+ USD | Six figures at scale | Opportunity plus risk |
| Enterprise or complex platform | 20,000 to 250,000+ USD | Dominant line in the budget | Opportunity plus risk |
The destination domain is a cost lever, not a formality
The destination domain is the one input that changes the size of the largest cost bucket. Migrate onto a freshly registered domain and authority restarts from zero, lengthening the recovery window the opportunity cost depends on. Migrate onto an aged domain that already carries relevant, earned authority and the inherited equity offsets the dip, shrinking both the opportunity window and the risk tail.
The published guides treat the new domain as a 10-to-50-dollar registration and move on. That framing is the field’s blind spot. The destination domain is not a formality. It is the variable that decides whether you are migrating into a vacuum or into a domain that search engines already trust for your topic.
| Decision | Fresh registration | Aged domain with relevant authority |
|---|---|---|
| Starting authority | Zero, restarts from scratch | Inherited from prior real use |
| Effect on recovery window | Longer dip, slower return | Offsets the dip, faster return |
| Effect on opportunity cost | Higher, recovery runs long | Lower, recovery runs shorter |
| Effect on risk-cost tail | Higher chance of falling short | Earned equity cushions the move |
| Direct price | 10 to 50 USD/year | Priced on the backlink profile |
| What you are buying | A name | A shorter, safer recovery |
The caveat is that the inherited authority has to be real and relevant, not an inflated metric on a junk drop. A clean, topically relevant aged domain offsets the recovery dip. A spam-flagged one imports a problem and lengthens recovery instead. This is why the destination domain is sourced from screened inventory, not an unvetted auction list. SEO Domains operates the curated marketplace where aged domains are screened across their backlink profiles and authority metrics before they are listed, so the destination domain is read before it is priced. Browse vetted candidates on the SEO Domains marketplace, and read how to evaluate a candidate in How to pick the new domain for migration.
How to cut the cost of a domain change, step by step
The way to cut the cost of a domain change is to attack the opportunity-cost window, because that is where the money is, not the build invoice. Six moves shrink the window and the risk tail at once: choose a strong destination domain, map every redirect one to one, test on staging, time the launch for low season, signal Google fast, and monitor for six months. Each move has a matching mistake that inflates the cost.
-
Choose a destination domain that already carries relevant authority
The destination domain sets the length of the recovery window. A clean aged domain with relevant earned authority offsets the dip; a fresh registration restarts from zero. Read the candidate’s backlink profile before buying, and source from screened inventory instead of an unvetted drop list. Browse vetted candidates on the SEO Domains marketplace.
The mistake: treating the destination as a throwaway 10-dollar registration, or buying an aged domain on an inflated metric with a toxic profile. The first lengthens recovery; the second imports a penalty.
-
Map every old URL to its new equivalent, one to one
A complete redirect map is the cheapest line and the highest-leverage one. Every indexed URL on the old domain gets a 301 to its closest match on the new domain. Build the sheet before launch, not after. The method is in Building the 301 mapping sheet.
The mistake: redirecting everything to the homepage, leaving gaps, or chaining redirects. Each one drops link equity and stretches the recovery window the opportunity cost is built on.
-
Validate the whole move on staging first
A staging environment catches broken redirects, lost pages, and template breakage before they cost live traffic. The redirect map, the templates, and the internal links are all verified before the switch goes public.
The mistake: migrating live with no staging pass. A redirect error found in production is a week of lost traffic; the same error found on staging is a five-minute fix.
-
Time the launch for your lowest-traffic season
The recovery dip lands whenever the switch happens, so it costs least when traffic and revenue are at their seasonal floor. A retailer migrates after the holiday peak, not before it.
The mistake: launching into peak season. The same percentage dip on peak revenue is the priciest version of the same migration.
-
Signal the change to Google immediately
Submit the move through the Search Console Change of Address tool and the new sitemap so Google processes the migration faster. The walkthrough is in Using GSC’s Change of Address tool.
The mistake: letting Google discover the move on its own. A delayed signal extends the indexing-disruption window of 30 to 60 days that DreamHost reports.
-
Monitor for a full six months and fix fast
The recovery window runs three to six months on a clean change, so monitoring runs the same length. Watch index coverage, redirect health, and ranking movement, and fix regressions the week they appear. The cadence is in Post-migration monitoring for 6 months.
The mistake: declaring victory at week two. A regression caught at week eight is far cheaper to fix than one discovered at month six when recovery has already stalled.
Common domain-change cost mistakes, and the fixes
The mistakes that blow a domain-change budget are a short, repeatable list, and each maps to one of the four cost buckets. The pattern is consistent: teams budget the visible direct line and under-budget the recovery window, the destination domain, and their own hours. The table below is the scannable reference, with the bucket each mistake hits and the fix that contains it.
| The mistake | Which cost bucket it inflates | The fix |
|---|---|---|
| Budgeting the build invoice only | Misses opportunity and risk entirely | Price all four buckets before approving the project |
| Migrating onto a fresh registration | Opportunity cost, longer recovery | Migrate onto an aged domain with relevant earned authority |
| Buying an aged domain on a raw metric | Risk cost, imports a toxic profile | Source a screened domain, read the profile before buying |
| Redirecting all old URLs to the homepage | Opportunity and risk, equity bleeds | A one-to-one 301 map for every indexed URL |
| Redirect chains and broken links | Opportunity cost, slow recovery | Direct single-hop redirects, validated on staging |
| No staging validation | Risk cost, errors hit live traffic | Full staging pass before the public switch |
| Launching in peak season | Opportunity cost on peak revenue | Time the switch to the seasonal traffic floor |
| Ignoring internal team hours | Indirect cost, hidden labour | Budget planning, QA, and asset-update hours explicitly |
| Forgetting old-domain renewal | Direct and risk, redirects expire | Hold and renew the old domain at least one year |
| Stopping monitoring at week two | Risk cost, stalled recovery | Monitor and fix for the full six-month window |
Stay or migrate: a break-even decision framework
A domain change pays off when the long-run benefit of the new domain exceeds the total four-bucket cost of getting there. The break-even test is direct: the change is justified when the recurring annual gain from the new domain, brand, or consolidated authority is larger than the one-time total cost spread over the period you will own the domain. When the gain is cosmetic and the organic revenue base is large, staying is the cheaper decision.
The framework forces the opportunity cost into the decision, where the field leaves it out. A rebrand driven by a merger or a legal requirement has a benefit that is hard to price but real. A rebrand driven by preference, on a site earning 20,000 dollars a month from search, has to clear a 48,000-dollar opportunity cost before it breaks even, and that bar reframes the conversation.
| Situation | Total four-bucket cost | Break-even verdict |
|---|---|---|
| Merger or acquisition forces one brand | High, unavoidable | Migrate; the benefit is structural, not optional |
| Legal or trademark requirement | High, unavoidable | Migrate; staying carries its own cost |
| Consolidating several domains into one brand | High up front, compounding gain | Frequently justified; see the consolidation guide |
| Cosmetic rebrand, large organic base | Opportunity cost dominates | Stay unless the brand gain clears the window |
| Moving onto a stronger aged domain | Higher direct, shorter recovery | Migrate if the authority gain is real and relevant |
The decision is rarely close when the trigger is structural and rarely justified when the trigger is taste. The framework’s value is making the opportunity cost visible so the choice is made with the real number in view. The equity-preservation detail for a brand change is in Rebranding without losing SEO equity.
Domain-change cost FAQ
The five questions established-site owners raise when they price a domain change, answered against the cited cost field and the four-bucket framework this guide uses.
Q1How much does it cost to change the domain on an established site?
The direct build runs from 1,500 dollars for a small site to 20,000 or more for a content-heavy or ecommerce property, per the 2026 Webyking, CMSMinds, and Cloudways cost guides. The total is higher once the opportunity cost of the recovery window is added. On a site earning 20,000 dollars a month from search, a 40 percent dip over six months forgoes 48,000 dollars, which exceeds a mid-site build.
Q2Why is the recovery window the biggest cost?
Because an established site earns revenue from rankings, and a domain change drops those rankings before they return. DreamHost reports an average recovery of 523 days and that 42 percent of migrations never fully recover. The revenue forgone during that window, computed as monthly organic revenue times traffic-loss percentage times recovery months, is usually larger than the build invoice.
Q3Does the new domain choice change the cost?
Yes, and it is the one lever that moves the largest bucket. A fresh registration restarts authority from zero and lengthens the recovery window. An aged domain that already carries relevant earned authority offsets the dip, shortening recovery and shrinking the opportunity and risk costs. The inherited authority has to be clean and relevant; a junk domain imports a problem instead.
Q4How long until traffic recovers after a domain change?
Bluehost and HawkSEM put a well-executed recovery at three to six months, with indexing of a sub-500-page site taking three to four weeks. DreamHost reports a 30 to 60 day indexing-disruption window and a 523-day average to full recovery across all migrations. A clean redirect map, a strong destination domain, and the Search Console change-of-address signal pull the timeline toward the shorter end.
Q5Is it ever cheaper to keep the current domain?
Frequently, when the trigger is cosmetic. A cosmetic rebrand on a site with a large organic revenue base has to clear the full opportunity cost before it breaks even, and that bar is high. When the trigger is structural, such as a merger, a legal requirement, or consolidating domains into one brand, the change is justified despite the cost because staying carries its own price.
Source the right destination domain for your migration
The destination domain is the single input that decides how steep the recovery curve is, and the recovery curve is where the cost of a domain change lives. A clean aged domain with relevant earned authority offsets the dip and shrinks the opportunity and risk costs. A junk domain or a fresh registration lengthens it. Sourcing the destination from a screened catalogue is the cheapest way to cut the largest bucket.
Everything in this guide converges on one decision. The build invoice is fixed by site size. Your team hours are fixed by complexity. The recovery window is the variable, and the destination domain is the lever that moves it. Migrate into earned, relevant authority and the dip is shallower and shorter; migrate into a vacuum and it runs long.
What a clean destination domain has to pass
A destination domain that shortens recovery instead of lengthening it survives a profile check before money changes hands. The signals that matter are the same ones that screen any aged domain acquisition:
- A clean, editorially earned backlink profile with no toxic inheritance, read before purchase.
- Topical relevance to the migrating site, so the inherited authority transfers to the right context.
- Cross-validated authority metrics, not a single inflated score, with a clean spam screen.
- A registration history checked through RDAP, which replaced WHOIS as the ICANN lookup standard on 28 January 2025.
A domain that fails these is a liability that lengthens recovery and raises the risk tail. A domain that passes is an asset that pays back its higher price by shrinking the largest cost bucket. SEO Domains operates the curated marketplace where aged domains are screened across exactly these signals before they are listed and priced, so the destination domain is read before it is bought.
