Skip to content
SiteMonk Learn
Esc
↑ ↓ navigate ↵ open ⌘J preview
On this page
  1. Start with the domain and its account
  2. Protect email and connected accounts
  3. Inventory content and functionality
  4. Map old pages to an appropriate destination
  5. Use a handover and launch checklist
  6. Agree on the switch before cancelling the old service
  7. What a move to SiteMonk involves
  8. Related

What to check before changing website providers

Confirm domain control, email, accounts, content and old page addresses before a website move. Use a handover checklist and agree on launch checks and responsibilities.

Before commissioning a replacement website, confirm that your business can control its domain, keep its email working and obtain the materials and account access the new team needs. Then agree on the move, the checks and who handles each step.

Missing access is a problem to resolve, not evidence on its own that a provider is deliberately preventing you from leaving. Ask for a written inventory and the steps needed to transfer control.

Start with the domain and its account

A domain is your public address. Confirm the registrar, the registration details, who can manage it, the renewal date and the recovery contact. The business should have appropriate control; routine access for a provider should not leave you dependent on one person’s private account.

ICANN Lookup can help identify the registrar and available registration information. Public records may be redacted, so verify the actual details and account arrangements with the registrar. A public lookup alone does not settle ownership or access.

Distinguish moving the website, changing DNS, transferring to another registrar and changing registration details. Ask which operations are necessary. Follow the registrar’s current process and applicable rules; see ICANN’s transfer guidance and CIRA’s guidance for .ca transfers .

Protect email and connected accounts

DNS connects the domain to services such as the website and business email. Before changing it, identify where it is managed, save the existing records securely and have the responsible person confirm which records must remain. A new website does not necessarily require moving the email service.

List the services the site depends on: Search Console, analytics, Business Profile where applicable, forms, booking, payments and newsletters. Record the account owner, billing contact and the access the incoming team requires. Use the service’s supported invitations and handover process instead of passing shared passwords around.

Inventory content and functionality

Collect copy, photos, documents, source code where available, and the rights to use those materials. A content export is not always a runnable website. Note the platform, hosting, forms, databases and external services needed for each important function.

If a platform or licence cannot be transferred, ask whether the next team must rebuild the function, replace the service or obtain a new licence. Agree on the scope and costs before work starts.

Map old pages to an appropriate destination

Keep useful existing addresses when practical. If an address must change, list its corresponding new page and the redirect to check. Include pages people use through bookmarks, emails, printed materials and external links, not only pages with search clicks.

An old page without a relevant replacement needs an explicit decision. Sending every missing page to the homepage is not a useful substitute. See URLs and language versions during a move .

Google may need to process changed pages and addresses; rankings can fluctuate during a move. Redirects help express the change but cannot guarantee unchanged visibility. See Google’s migration guidance .

Use a handover and launch checklist

Item Evidence to collect Who needs to act
Domain Registrar, registration details, renewal and account/recovery access Business owner and registrar; providers assist with authorized access
DNS and email Current records, email provider, required settings and planned changes People responsible for DNS and email
Content and assets Exports, source where available, files and usage rights Business owner and outgoing provider
Functions and services Dependencies, accounts, billing, data and transfer limitations Outgoing and incoming maintainers with the account owner
Old and new addresses Page inventory, matching destinations and checks Incoming website team, with business decisions confirmed
Launch Approved version, change window, verification and recovery plan Named launch owner and the people approving the result

This is a template, not a completed migration record. Mark unknowns and assign an owner rather than assuming an account or export will be available.

Agree on the switch before cancelling the old service

Ask how the existing site will remain available while the replacement is prepared, which access must stay active and when you can safely end old subscriptions. Set a change window and a recovery plan for the parts that can be restored. Restoring website files does not undo transactions made in another system.

After the switch, verify public pages, old links, email, form delivery and the connected tasks in scope. Record actual results and outstanding issues. Domain control reduces dependence on a provider; it does not eliminate migration work or all interruption risk.

What a move to SiteMonk involves

We start by checking domain control, the existing site and the functions worth keeping. A standard rebuild uses our $4,920 build price before tax, within a reasonable scope agreed in writing; larger or different projects are assessed separately. Care begins at launch. See current pricing .

We prepare the replacement before the agreed switch, plan the relevant old-address mappings and verify the new result. Dependencies, access and the outgoing provider’s arrangements affect what is possible, so the proposal should identify unresolved items.

Your domain stays under your control. If you later leave SiteMonk, you receive the full source and the handover information described in our workflow . Cancellation and handover follow the agreed terms.

Source guidance and SiteMonk scope checked on October 27, 2026.