Quick answer: A dealership can change website provider without losing its domain or unnecessarily disrupting its business, but only with a planned migration. Secure domain and DNS access, inventory exports, URL mapping, working enquiry routes, and a tested rollback before making the new site live. Never cancel the old service before confirming what will happen to stock, email and indexed pages.
Moving a dealership website is not just a design change. The live website may be tied into a stock feed, business email, analytics, phone buttons, enquiries and hundreds of vehicle URLs. A careless transfer can produce broken pages, stale vehicles or missing customer messages even when the new homepage looks excellent.
This guide provides a step-by-step migration plan for independent Northern Ireland car dealers. The principles also apply to dealerships elsewhere in the UK.
Start by listing everything you currently use
Before accepting a new provider's quote, list every function supplied by the old service. Your website may include hosting, domain management, stock synchronisation, email, enquiry forms, calendar integration, analytics and advertising-related landing pages. Some of these may be provided by third parties, with the website provider simply acting as administrator.
Record the domain registrar, DNS provider, existing hosting account, email service, stock system, website CMS, analytics accounts and any paid-ad landing URLs. Identify which logins belong to the dealership and which are controlled by the previous supplier.
Do not share passwords unnecessarily. Use appropriate administrative invitations or temporary credentials where supported, and remove access that is no longer required after the migration.
Secure the domain and email arrangements first
Your business's domain name is one of its most important digital assets. Confirm the registrant or controller details and your ability to manage DNS. Where the previous supplier manages the domain, request written instructions for transfer or delegation.
Email is particularly easy to overlook. A change to nameservers can affect MX, SPF, DKIM and DMARC records, potentially interrupting business mail or deliverability. Moving the website does not automatically require moving email. Document the current mail configuration before changing DNS.
If anyone tells you to “just point the domain to us”, ask exactly which records will change and who will test them. Keep a record of the previous working values so you can revert if necessary.
Export stock and business content
Request useful exports of vehicle data, photographs and business content where your agreement permits. Confirm whether the export includes stable vehicle IDs, image ordering, descriptions, prices, statuses and historical URLs.
Ask whether staff are allowed to continue editing the old system during migration. If so, establish a freeze or final delta-sync process so the new platform does not launch with yesterday's prices. Take a final inventory count and compare it with the new site before switching.
Preserve actual dealership information: address, opening arrangements, warranty descriptions, aftersales details, privacy content and contact methods. Do not silently copy another provider's protected design or software code as if it belonged to the dealership.
Map the old URLs to the new ones
SEO migration requires more than submitting a new sitemap. Export or crawl existing URLs and group them into: homepage, stock list, vehicle detail pages, editorial resources, dealership policies and any obsolete pages.
Where a page has a true relevant successor, use a permanent redirect to that new destination. Keep paths stable where practical. For an obsolete page with no suitable replacement, an appropriate 404 or 410 response may be better than sending everyone to the homepage.
A sample URL mapping sheet might contain:
| Previous URL | New destination | Action |
|---|---|---|
/used-cars |
/cars-for-sale/ |
Relevant 301 redirect |
/vehicle/example-stock-123 |
/cars/example-stock-123/ |
301 if corresponding car remains available |
/about-us |
/about/ |
Relevant 301 redirect |
/old-promotion |
No successor | Appropriate removal response |
These are example paths, not PureCar's actual routes. Google explains that redirects are signals for canonicalization, and unrelated homepage redirects may not preserve the relevance of an individual page. See Google's redirect guidance.
Test the new website before switching DNS
A temporary staging domain or preview URL allows staff to inspect the site without disturbing customers. Confirm it is not accidentally indexable alongside the real site. Perform a representative test of stock, images, descriptions, phone links, enquiry delivery and mobile search.
Check both the visible content and the HTML of important pages. Verify titles, canonicals, sitemap generation and robots settings. Avoid publishing the staging hostname as the canonical on live pages.
If the platform supports multiple stores or domains, also confirm the correct dealership branding and contact details appear on every page. A shared template can accidentally retain another dealer's phone number, logo or address.
Plan the cutover with a rollback
Choose a sensible time, identify who can make DNS changes and document a rollback path. Take a backup of the previous working configuration and record who is responsible for monitoring the launch.
Once the new site is live, test the exact public hostname rather than relying on the staging preview. Check the homepage, stock list, several vehicle detail pages, common redirects, sitemap, forms and mobile navigation. Make a telephone call from the site and submit a genuine test enquiry to the intended inbox or dashboard.
Do not declare success merely because the homepage returns HTTP 200. One broken stock integration can matter more than a cosmetic issue.
First 30 days after a switch
Monitor Google Search Console for crawling and indexing problems, missing pages, unexpected canonical selections and redirect loops. Check stock counts and freshness daily at first. Verify enquiries are arriving and that previously used phone numbers or email addresses are not still embedded in templates.
Keep the old hosting and service agreements available until contractual and operational obligations are understood. Cancel services deliberately and only when replacement functions have been verified.
Organic visibility can fluctuate after migrations; there is no guaranteed ranking preservation. Monitor relevant traffic and enquiries over a reasonable period rather than judging the project by one day's positions.
Questions to ask the new provider
- Will you import our actual stock system and all required fields?
- Who handles 301 redirects, and is the URL map included in the quote?
- Can we retain our current domain registrar and email service?
- How long can we review a staging copy before launch?
- What happens if a feed fails immediately after the cutover?
- Who owns the new website content and who controls the domain?
- What support is available during the changeover and after launch?
- Can you provide an itemised list of charges and cancellation terms?
Common migration mistakes
Changing domain and design at once without a compelling need. Every unnecessary change creates another thing to diagnose. Preserve important URLs and business details where practical.
Migrating the stock count but not its accuracy. Fifty imported records are not evidence that prices, image order or sold statuses are correct.
Forgetting email. Domain DNS changes can disrupt messaging even when the website appears normal.
Using a catch-all redirect. A broad redirect can mask missing individual pages and send buyers to irrelevant content.
Losing the old URL inventory. Without it, redirects are guesswork and historical links are difficult to protect.
Assuming the new site's SEO package includes migration. Ask for a specific list of work, including the redirect plan and post-launch checks.
Sources and further reading
- Google Search Central: redirects and Google Search
- Google Search Central: canonical URL guidance
- Google Search Central: SEO Starter Guide
- PureCar: website cost guide
Disclosure: PureCar also provides dealer websites. This checklist is intended to help dealers evaluate any provider, including PureCar. It is not a promise that every migration will retain all rankings or that every integration is available by default.