SMB DNS migration: take back control before you cancel your old provider

Changing web providers doesn’t start with moving the site

The domain isn’t just the site’s address. It often involves subdomains, SSL certificates, forms, transactional emails, redirects and sometimes even security alerts. Closing the old provider’s account too quickly can leave pieces running in the wrong place.

Registrar, DNS and hosting: three roles not to mix up

In many cases, the confusion comes from vocabulary. The registrar is where the domain name is registered. Authoritative DNS is the service that answers questions like “where does this name point?” Hosting is the server or platform that serves the site. These roles can be with the same provider, but they don’t have to be.

When a business says “our domain is with the agency,” it sometimes means the registrar, sometimes the DNS, and sometimes just the site. Before a migration, you need to know exactly who controls what. Otherwise, the business can end up with a site that has moved but DNS that’s still tied to the old provider.

Old subdomains are blind spots

A domain can pile up leftovers. An old form, a test subdomain, FTP access, a temporary redirect, a forgotten email record. Years later, these records may still point to a platform that shouldn’t be part of the picture anymore. This isn’t just cosmetic cleanup. It can trigger alerts, leave an old attack surface exposed or complicate support.

A well-managed migration should include an inventory of records. Useful entries are kept and validated. Legacy entries are deleted or properly redirected. Emails, forms and certificates are tested. It’s less visible than a brand-new home page, but it’s often what prevents incidents after launch.

You also need to check which accounts will receive alerts. A domain can send renewal notices, verification codes or SSL notifications to an address nobody monitors anymore. This mundane detail can delay a migration or force a needless scramble on cutover day.

Don’t cancel the old service before validation

The overlap sometimes costs a few extra days. It’s better to pay for that short delay than to find out too late that a form was still sending through the old server or that an important subdomain wasn’t recreated. The right sequence is simple: transfer or confirm access, copy the records, validate the new path, test forms and emails, and only then close the old service.

The same logic applies to web hosting. A site can respond with HTTP 200 and still have missing pieces: a certificate that wasn’t renewed properly, a missing redirect, a form email that doesn’t get delivered, a cache showing an old version or an old subdomain that’s still live.

A simple checklist before the cutover

• Access: who controls the registrar, DNS, hosting and mailboxes?
• Inventory: has every subdomain been explained or cleaned up?
• SSL: are the certificates valid on the new path?
• Forms: do messages leave from the right server and arrive at the right email address?
• Propagation: have you planned a period where the old and new paths coexist?
• Client sign-off: has someone tested the important pages and features before the shutdown?

It’s not glamorous work. Nobody notices a DNS record that was properly deleted. But everyone notices when a site, a form or a certificate breaks after a migration.

Take back control, then simplify

A well-managed DNS migration is a good opportunity to reduce your dependence on an old provider. Centralizing DNS in an account the business controls, documenting access and cleaning up leftovers saves you from repeating the same research with every change.

If you’re preparing a change of website, hosting or provider, Infotech Canada can review your domains, DNS, certificates and forms before the cutover. We can also note which accounts are responsible, so critical access doesn’t stay stuck in someone’s personal mailbox. You can book a meeting to validate the sequence. The goal is simple: shut off the old service only when the new path is truly ready.

Changing web or hosting providers?

We can check your domains, DNS, certificates and email before the old service is shut off.

Book a meeting

Have a specific question about your situation? Write to us.