The dealer migration tax most principals never see

A dealer migrates from one major dealer platform to another. The new vendor's onboarding team manages the cutover. Launch happens on schedule. The dealer principal is told the migration is complete. Sixty days later, organic traffic is down 47 percent and nobody can explain why. Twelve months later, traffic has recovered to 78 percent of where it was. The other 22 percent is gone forever.

That story is not unusual. It is the median outcome for dealer platform migrations handled by either platform's onboarding team. The migration tax is real, it is large, and almost no dealer principal sees it on the invoice because it does not arrive as a line item. It arrives as a quiet drag on lead volume that the agency blames on seasonality, the OEM blames on the market, and the platform calls "post-launch normalization."

Where the equity actually leaks

A dealer website is a structured database of pages: VDPs for every vehicle, SRPs for every body style and trim, model landing pages, finance pages, service pages, blog posts, location pages. Over years of being indexed, that page graph accumulates SEO equity through external backlinks, internal link patterns, dwell time signals, and ranking history. When a migration happens, every URL in that graph either stays the same or changes. Most change.

A clean migration maps every old URL to a new URL via a 301 redirect. The redirect tells Google the page has moved permanently and tells the search engine to transfer the accumulated equity to the new location. A botched migration does this for the obvious URLs (the homepage, the main service page) and misses or mismaps thousands of inventory URLs, archived pages, model landing pages from prior years, dealer-authored content. Those URLs return 404. The equity attached to them evaporates.

The eighteen common failure modes

We have catalogued eighteen distinct technical failures we encounter post-migration. They group into three phases:

Before the cutover

URL structure changes without a complete redirect map. Schema markup not migrated. Sitemap not migrated or never resubmitted to Search Console. Google Search Console verification lost on the new domain. Google Business Profile disconnected from the new site URL. Backlink inventory not catalogued, so the team has no baseline for what is supposed to redirect.

During the cutover

Inventory feed cutover errors that drop vehicles from Google Vehicle Listings. Tracking pixels and tags not migrated, so 30 days of conversion data are lost before anyone notices. Form integrations broken, sending leads into a void. Image references broken, inflating LCP and breaking visual integrity. Robots.txt regression that accidentally blocks crawlers from the new staging environment that was promoted to production. HTTPS and redirect chain regressions that introduce 5+ hops on previously direct paths.

After the cutover

Indexing recovery stalls because the redirect map was incomplete. Programmatic SEO pages, model-by-trim and location-by-service, lost entirely because the new platform has no analog. Hreflang lost on bilingual sites. Reviews and testimonials not migrated. Customer accounts and saved searches lost, eroding repeat visitor equity. The old vendor's tracking still firing in parallel for months, polluting GA4 with duplicate events.

Why the obvious teams cannot prevent it

The new platform's onboarding team is incentivized to ship the launch on schedule. SEO continuity is not their KPI. Your marketing agency is incentivized to keep the campaigns running, but they almost never have the technical access or the project authority to manage a multi-vendor cutover. Your internal team, if you have one, is busy running the dealership and does not have the platform-specific expertise to catch the regressions before they ship. Your OEM has a co-op program but no operational role.

The result is a coordination gap between nine stakeholders (old vendor, new vendor, OEM, agency, dealer principal, marketing director, IT, BDC, compliance), none of whom owns the migration end to end. The work falls between the chairs.

The math nobody runs upfront

For a single-rooftop dealer with $30,000 of monthly organic traffic value and a typical 9-month recovery curve, the lost organic revenue alone runs into six figures. Add SEO recovery agency fees ($25K-$45K), developer remediation for redirect maps and schema fixes ($12K-$25K), and ad efficiency loss during the recovery window (often $20K-$50K), and the total exposure for a botched migration sits between $150,000 and $400,000. For a multi-rooftop group, multiply.

None of that shows up on the migration invoice. It shows up on the year-over-year P&L as a soft trend that the dealer principal cannot diagnose.

The playbook to avoid it

Run a complete pre-migration SEO audit before the contract is signed with the new platform. Catalogue every indexed URL, every backlink, every schema implementation, every tracking integration, every programmatic page set. Build the redirect map before the new platform's setup begins, not after. Coordinate the cutover day with all nine stakeholders aligned on the launch checklist. Verify schema, sitemap, indexing, tracking, and forms within 48 hours of launch. Run a 90-day recovery monitoring report.

That is the work we run end to end on the Migration Service. Pre, during, and post. The price is a small fraction of what a botched migration costs. If you are planning a platform switch, currently in one, or recovering from one, the discovery call is free and we will tell you whether your situation is salvageable, what we would do, and what it would cost.