Author: williamwhite

  • CASL Express vs Implied Consent: What’s the Difference?

    CASL Express vs Implied Consent: What’s the Difference?

    Express consent is a clear opt-in that doesn't expire, while CASL implied consent comes from an existing relationship and runs out, typically after 2 years for purchases and 6 months for inquiries. The difference determines whether you can keep sending commercial email or need to stop and ask for express permission.

    A common situation looks simple. You sell services, a customer bought from you in March 2025, and you want to email them about a seasonal promotion. You may have implied consent, but you need to know exactly when the qualifying relationship began and whether the relevant window remains open.

    That consent clock is where many small businesses get caught. A contact can remain in your email platform long after the legal basis for marketing messages has expired. We'll explain the difference between express and implied consent, how to calculate expiry, and what records you need to support your decision.

    Why CASL Consent Rules Matter for Your Email List

    Canada's Anti-Spam Legislation, or CASL, regulates commercial electronic messages. A message generally falls into this category when it encourages participation in commercial activity, such as buying a product, booking a service, or responding to a promotion. The rules matter whether you're a large company, a local shop, or a solo consultant emailing business contacts.

    The practical distinction is straightforward. Express consent means the recipient actively says yes, usually through a form, checkbox, or written agreement. Implied consent comes from a qualifying relationship or circumstance, and it lasts only for a defined period. The CRTC's CASL guidance explains these consent categories and their time limits.

    A past purchase can create a lawful basis for relevant commercial email, but it doesn't give you an evergreen marketing pass. An inquiry creates a shorter window, and a publicly posted business email has narrow conditions attached. If you can't identify the relationship, its start date, and the consent basis, your mailing list needs attention before your next campaign.

    Practical rule: Treat every implied-consent contact as a dated record, not as a permanent subscriber.

    CASL also places the responsibility on the sender. The person sending, causing, or permitting the message must be able to prove consent, as stated in the CRTC's enforcement advisory on consent records. That makes record keeping part of your email process, not an administrative task you can postpone.

    For a broader explanation of the law, see our guide to Canada's Anti-Spam Legislation. The key takeaway here is simple: use express consent whenever possible, and track implied consent from the exact event that created it.

    What Express Consent Means Under CASL

    Express consent is an affirmative, informed opt-in. The recipient takes a clear action to agree to receive commercial electronic messages from you. A newsletter form, an unchecked marketing checkbox during checkout, or a written service agreement can all provide a practical way to request that permission.

    The wording matters because the recipient should understand what they're agreeing to. A vague statement such as “You'll receive updates” leaves too much uncertainty. A clearer version identifies your business and describes the type of messages you plan to send.

    For example, a signup form might say that the person agrees to receive product news, promotions, and business updates from your company. The form should make the choice voluntary and separate from actions such as creating an account or completing a purchase.

    What a valid opt-in should show

    Use a dedicated, unchecked checkbox where possible. The person should click or select it themselves, rather than being enrolled automatically through another action.

    Avoid wording that hides marketing permission inside unrelated terms. “By placing your order, you agree to receive promotional email” combines a purchase with a separate marketing decision. A clear form gives the recipient a real choice.

    The consent request should also identify the sender and explain how the recipient can withdraw permission. Every commercial message still needs a working unsubscribe mechanism, so your signup process and sending templates should support the same expectation.

    An infographic explaining the requirements for express consent under Canada's Anti-Spam Legislation for commercial electronic messages.

    A written agreement can work when it contains a specific email permission clause. Keep the signed agreement, the version of the clause, and the date it was accepted. If someone gives verbal permission, document who agreed, when they agreed, what you explained, and how you recorded the decision.

    Why express consent reduces administration

    Express consent doesn't expire under CASL, although the recipient can withdraw it. That makes it the durable basis for a newsletter or long-term marketing list.

    It also removes one particular burden. You don't need to calculate a two-year purchase window or a six-month inquiry window for that consent basis. You still need proof, accurate sender information, and a functional unsubscribe process.

    Capture express consent whenever you can. It gives your recipient a clearer choice and helps you avoid managing a separate expiry date for every contact.

    What Is CASL Implied Consent

    CASL implied consent is permission inferred from a qualifying situation rather than a direct opt-in. The CRTC identifies several routes, including an existing business relationship, an existing non-business relationship, and a publicly published email address that meets specific conditions.

    An existing business relationship can arise from a purchase, lease, or written contract. For example, if a customer buys equipment from your shop, you may have a basis to send relevant commercial messages during the applicable period. Keep the purchase record because the transaction date starts the consent clock.

    An existing non-business relationship can involve activities such as membership, donations, or volunteer work. The relationship still needs to fit the applicable CASL conditions, and you shouldn't assume that every person who has ever interacted with your organisation belongs on a marketing list.

    Publicly posted addresses need careful handling

    Finding an email address on a company website doesn't automatically create broad permission. The CRTC's guidance says the address must have been published without a statement refusing unsolicited commercial messages, and your message must relate to the person's business or official role.

    Suppose a law firm publishes a general address for client enquiries. That doesn't give you a free pass to send unrelated promotions. Even when a published address qualifies for implied consent, your message should connect directly to the recipient's role or the purpose for which the address appears.

    A public email address is a narrow signal of relevance, not an evergreen subscription.

    The same caution applies to business cards and contacts gathered at events. You need to understand the context and the relationship before adding the address to a recurring campaign. A contact who asks for a product catalogue is different from someone who only exchanges a greeting at a conference.

    Implied consent also doesn't mean every message is appropriate. Keep communications connected to the relationship that created the consent. If the relationship is weak, unclear, or difficult to document, ask for express consent instead.

    Your list should record the basis for each contact. Label a person as a purchaser, an inquirer, a member, or a qualifying published contact, rather than placing everyone into one undifferentiated marketing segment.

    How Long Each Consent Type Lasts

    The consent clock begins with the event that creates the relationship. Record that date, rather than relying on the date someone entered your email platform or received a staff tag. The exact start date determines whether a later message is still covered.

    For a purchase, lease, or written contract, implied consent generally lasts 2 years. The CRTC's consent infographic explains that the period starts with the event that began the relationship, such as purchasing a good or service.

    For example, a customer who made a qualifying purchase in March 2025 has a purchase-based consent period measured from that transaction. Your records should identify the transaction date and relationship type, so your team can check whether a proposed campaign falls within the permitted window.

    An inquiry or application that does not lead to a transaction generally creates implied consent for 6 months. Someone who emails in March 2025 to ask about your service, then never buys, should not be treated like a customer with a purchase-based relationship. Store the inquiry date separately and apply the shorter period.

    Ongoing accounts change the starting point

    For subscriptions and memberships, the CRTC states that the clock starts when the relationship ends, as described in its guidance on implied consent periods. An active account therefore does not have a simple expiry date based on its signup date. Keep a reliable record of when the relationship ended before calculating the review or expiry date.

    A spreadsheet can serve a small list, provided it contains more than a name and email address. Record the qualifying event, event date, relationship category, and the date your team must review the contact. These fields turn a vague sense of familiarity into an auditable consent history.

    CASL's transition history also affects older databases. Guidance in Canada stated that implied consent for certain pre-existing relationships was valid only until July 1, 2017. The standard periods then became the main rule for new and continuing relationships. Do not reactivate an old list based only on its age or past familiarity.

    A visual infographic explaining different types of consent and how long each one lasts.

    As the window approaches its end, request express consent while you still have a lawful basis to send that request. Once implied consent expires, stop sending commercial messages unless another valid basis applies.

    Express vs Implied Consent at a Glance

    Dimension Express Consent Implied Consent
    How it's obtained The recipient actively opts in through a form, checkbox, or documented agreement A qualifying business relationship, non-business relationship, or properly published business email
    Does it expire It doesn't expire, unless the recipient withdraws it Yes, the applicable relationship window ends
    Expiry window No CASL expiry period applies Generally 2 years for a purchase, lease, or written contract, and 6 months for an inquiry, according to CRTC consent guidance
    Evidence needed Consent date, method, wording, and supporting record Relationship type, triggering event, exact date, and supporting record
    Risk when records are thin You may not be able to prove the opt-in You may lose both the relationship evidence and the lawful time window

    Express consent suits newsletter signups and marketing lists you expect to maintain. A visitor who checks an unchecked box after reading a clear description has made a direct choice. You still need to keep the record, but you don't need to manage a relationship expiry date for that consent.

    Implied consent can make sense for relevant follow-ups after a purchase or inquiry. It can also support a carefully timed campaign to an existing customer, provided the relationship remains documented and the window is open.

    The common mistake is treating implied permission like express permission. A public email address isn't a standing invitation to send unrelated offers, and an old purchase doesn't stay fresh because the contact remains in your customer database.

    Use the table as a decision aid before you send. If your team can't name the consent basis and identify the event date, pause the campaign and investigate the record.

    How to Capture and Prove Consent

    The sender carries the burden of proof under CASL. A contact's presence in Shopify, HubSpot, Outlook, or a spreadsheet doesn't prove that the person consented to receive your commercial messages.

    A defensible record connects the person to a clear event. At minimum, capture the email address, consent basis, date, method, and the wording shown when the person opted in. For implied consent, add the transaction, contract, membership, donation, or inquiry that created the relationship.

    Build a record at the point of collection

    A small business can create a workable process without a complex compliance system:

    1. Timestamp each event. Store the date of every purchase, lease, contract, inquiry, subscription end, or membership end in the system that holds the original record.

    2. Preserve signup evidence. Export form submissions with the date and retain the exact consent language. If your form changes, keep the older version linked to earlier submissions.

    3. Tag the consent basis. Separate express consent from purchase-based, inquiry-based, and other implied-consent categories in your email platform.

    4. Review approaching expiry. Create a regular review queue for records nearing the end of their applicable window.

    5. Log withdrawals. Keep a suppression record so an unsubscribed address doesn't return through a later import.

    The exact language matters because a current form may not match the wording a person saw when they subscribed. A contract or order record can support implied consent, but it doesn't replace the need to show when the relationship began.

    An infographic titled How to Capture and Prove Consent, outlining six key steps for managing user privacy compliance.

    Act before implied consent expires

    If a purchase-based relationship is nearing its expiry, invite the person to opt in expressly. If an inquiry-based relationship is nearing its shorter limit, make the same decision sooner. Your options are simple: obtain express consent while you can, or stop sending commercial messages when the implied basis ends.

    Don't rely on memory or an employee's explanation of what happened. The CRTC's record-keeping guidance makes proof the sender's responsibility.

    Privacy governance also includes how you store and manage personal information. Review the practical connection with PIPEDA compliance for Canadian businesses, especially if several tools hold copies of your customer and subscriber data.

    Common Questions About CASL Consent

    What's the difference between express consent and implied consent under CASL?

    Express consent is an active opt-in where the recipient clearly agrees to receive commercial messages. Implied consent comes from a qualifying relationship such as a purchase or inquiry, and it's time-limited. Express consent doesn't expire unless withdrawn; implied consent typically lasts 2 years for purchases or 6 months for inquiries.

    How long does implied consent last for a purchase?

    Implied consent from a purchase, lease, or written contract generally lasts 2 years from the transaction date, according to CRTC guidance. Once this period ends, you need express consent to continue sending commercial messages.

    When do I need to ask for express consent instead of relying on implied consent?

    You should request express consent once an implied-consent window is approaching its end, or when a contact doesn't fit a clear qualifying relationship. Implied consent requires that you identify and date the original event (purchase, inquiry, etc.). If you can't document that event, ask for express consent instead.

    What records do I need to prove CASL consent?

    Keep the email address, consent basis (express or implied), the date of the event that triggered it, and the method by which you obtained it. For express consent, preserve the exact wording the recipient saw. For implied consent, keep the purchase record, contract, inquiry email, or other evidence of the qualifying relationship.

    Can I keep sending emails to someone after their implied-consent window expires?

    No. Once implied consent expires, you must stop sending commercial messages unless you have another valid basis, such as express consent. The CRTC guidance makes the sender responsible for tracking expiry dates and respecting them.

    Best Practices and a Simple CASL Checklist

    A clean list starts with a clear record for every address. Before your next campaign, identify why each person is eligible to receive it and find the event that supports that reason.

    Use this checklist as a working review:

    • Record the consent basis: Mark each contact as express consent or a specific implied-consent category.

    • Date-stamp the relationship: Save the exact purchase, lease, contract, inquiry, application, subscription-end, or membership-end date.

    • Set review reminders: Track the 2-year purchase, lease, or contract window and the 6-month inquiry window using the applicable CRTC rules.

    • Ask during checkout: Offer a separate, unchecked marketing opt-in instead of assuming a purchase means newsletter permission.

    • Preserve the wording: Keep the form, checkbox text, agreement clause, or other language the recipient saw.

    • Remove expired contacts: Stop commercial messages when the applicable implied-consent window ends unless you've captured express consent.

    • Protect unsubscribes: Keep a suppression record so an address doesn't return through a list import.

    Legal permission isn't the same as reader interest. Sending frequent or poorly targeted messages inside an implied-consent window can still annoy people and increase complaints. Relevance, clear identification, and an easy way to leave help protect the relationship as well as your compliance process.

    Your email provider also affects your broader privacy habits. A service that keeps Canadian business data under Canadian jurisdiction can make it easier to organise access, retention, and vendor reviews. That doesn't make your email campaigns CASL-compliant by itself, but Canadian data sovereignty guidance can help you assess where business information is stored and who can access it.

    Keep your process small enough for your team to follow. One well-maintained consent register is more useful than a complex workflow nobody updates.

    The habit that matters most: date-stamp everything. Without the event date, you can't reliably manage CASL implied consent or know when it has expired.


    Typewire provides ad-free, encrypted email hosted in Canada, with privacy-focused tools for individuals and small businesses. If you want a Canadian email provider with custom domains, no data mining, and infrastructure you control more closely, visit Typewire and start with the 7-day free trial.

  • Moving Away from Big Tech Email and How to Make the Transition Smooth. Here’s How:

    Moving Away from Big Tech Email and How to Make the Transition Smooth. Here’s How:

    Something broke with your email. A launch didn't send. You discovered your "free" inbox is actually a data collection tool. Or you just got tired of your business email living inside Google or Microsoft's platform. Whatever happened, you're here because the setup you've got isn't working anymore.

    The good news is that moving away from big tech email and how to make transition smooth isn't a mystery project. It's mostly a sequencing problem. If you pick the right provider, prepare your accounts before changing anything, and treat the switch like a small go-live, you can move without losing mail, contacts, or your sanity.

    Most rough migrations happen for predictable reasons. People change MX records too early, forget which services use the old address for password resets, or skip authentication records like SPF and DKIM because the DNS panel looks intimidating. A smooth move comes from doing the boring steps in the right order.

    Planning Your Move From Big Tech

    A lot of business owners don't switch because they love migration projects. They switch because the old setup starts getting in the way. A common situation is hitting Gmail's sending limits during a busy week, or realising your inbox is part of a larger ad-driven system that doesn't line up with how you want your business data handled.

    Privacy is often the trigger. Most people don't realize how deeply free email providers scan inbox content for advertising and data profiling. If you thought "free email" meant "no monthly bill" and nothing else, that gap usually catches up with you eventually.

    An infographic comparing the benefits of moving away from big tech email services versus current challenges.

    Choose based on business model, not just features

    The first filter we use is simple. Ask how the provider gets paid. If the service is funded by subscriptions, the incentives are usually cleaner. If the service sits inside a giant ad ecosystem, your email may be part of a much broader data picture.

    The second filter is jurisdiction. For many Canadian businesses, keeping email data under PIPEDA is a practical requirement, not a branding preference. Jurisdiction affects disclosure rules, provider obligations, and how comfortable you feel storing client conversations there.

    Practical rule: Don't pick a new provider because the homepage sounds private. Read the privacy policy, check where data is hosted, and confirm whether the company runs its own infrastructure or rents space inside another large cloud.

    Build a simple scorecard before you move

    If you compare providers casually, everything starts sounding the same. A short scorecard forces clarity. Rate each option on privacy policy, data residency, custom domain support, IMAP and SMTP support, migration help, daily sending limits, spam filtering, and ease of use for a non-technical person.

    Here's a practical side-by-side view.

    Factor Big Tech Providers (e.g., Gmail, Outlook) Privacy-First Providers (e.g., Typewire)
    Business model Often tied to a wider platform or ad ecosystem Usually subscription-based email service
    Data handling Can sit inside broader account profiling systems Typically focused on email as a paid product
    Jurisdiction control May place data under foreign legal regimes Some providers offer Canadian data residency
    Sending flexibility Consumer accounts may have stricter limits Paid business-focused plans often allow more flexibility
    Custom domains Available, sometimes behind business setup tiers Often central to the product
    Simplicity Familiar interface, but tied to larger ecosystems Can be simpler if you only want email
    Privacy posture Convenience-first Privacy-first

    If you want a broader view of why people are reconsidering mainstream inboxes, our piece on why people are moving away from big tech email in 2026 adds context.

    What works and what doesn't

    What works is picking a provider that matches your real use. If you run a small company, a custom domain, standard protocols like IMAP and SMTP, clear admin controls, and straightforward support matter more than a pile of bundled extras.

    What doesn't work is switching to a service that is technically private but too awkward for daily use. Proton Mail, for example, is a valid option for many people, but some non-technical users find the setup and workflow more involved than they expected, especially when they want standard desktop client compatibility or a simple business rollout. The right move isn't the most extreme privacy posture on paper. It's the one you'll keep using properly.

    Your Pre-Migration Checklist

    Before you touch DNS, export everything you may need later. This step feels slow, but it prevents the kind of problems that turn a clean migration into a weekend emergency. Email moves are easier when you treat them like packing before a move, not like throwing things into boxes after the truck arrives.

    A four-step checklist for a smooth email migration process, displayed with icons and clear instructional text.

    Back up mail, contacts, and calendars first

    Export your old mailbox before starting the move. If your current provider supports mailbox export, use it. If not, a desktop client such as Thunderbird or Apple Mail can often sync a local copy through IMAP, which stands for Internet Message Access Protocol. In plain terms, IMAP lets an email app see and organise mail stored on the server while also keeping a local synced copy.

    Do the same for contacts and calendars. Contacts usually export as CSV or vCard files. Calendars usually export as ICS files. Save them somewhere separate from the email account you're about to leave.

    Backups aren't pessimism. They're what let you fix a bad migration without panic.

    Audit every account tied to the old address

    This is the step people skip, and it causes the most frustration later. Your email address isn't just where messages arrive. It's also the recovery path for banking logins, bookkeeping tools, domain registrar access, payroll systems, social media, e-commerce platforms, and software subscriptions.

    Make a working list before the move:

    • Financial accounts: Banking, invoicing, accounting, and payment processors.

    • Business infrastructure: Domain registrar, web host, SSL notices, and form tools.

    • Identity services: Password managers, two-factor backups, and recovery addresses.

    • Public-facing accounts: Social media, directories, and marketplace profiles.

    Change the important ones first. Start with the domain registrar and any security-critical accounts. If you lose access to your domain account during an email migration, everything gets harder.

    Clean up the inbox before you copy it

    A migration is a good time to reduce clutter. Archive old newsletters, delete obvious junk, and merge duplicate contacts. You don't need a perfect inbox, but moving less mail usually means fewer sync issues and a cleaner start.

    It also helps to notify a small group of important contacts early. Tell your accountant, key clients, suppliers, and team members that a new address is coming. They don't need a long explanation. They just need to recognise the new sender when the first message lands.

    Keep a simple migration file

    Use a plain document or spreadsheet and track four things: exports completed, critical accounts updated, contacts notified, and test messages sent later during cutover. Non-technical owners often try to keep this in their head. That works until one forgotten password reset email goes to the old inbox two weeks later.

    Setting Up Your New Email Foundation

    This is the point where many people assume they need an IT department. You don't. You do need patience and the right order. The core job is to connect your domain to your new email provider and publish a few DNS records so other mail servers trust what you send.

    A custom domain is the part after the @ in your email address, like yourcompany.ca. If you haven't bought one yet, our guide on how to buy an email domain for ultimate privacy and security covers the practical choices.

    A person setting up a custom domain for a website using the Brandify configuration interface on a computer.

    Start with your domain and DNS

    Your domain registrar is where you bought the domain. That may be Hover, Namecheap, GoDaddy, or another registrar. Inside that account, you'll find DNS, or Domain Name System, settings. DNS is like the internet's address book. It tells the rest of the internet where to send your web traffic and your mail.

    For email, the most important record is the MX record. MX stands for Mail Exchange. It tells other mail servers which provider should receive mail for your domain.

    Why this matters: If your MX record points to the wrong place, mail won't arrive in the new inbox no matter how polished the rest of the setup looks.

    Add the trust records that protect deliverability

    After MX, you'll usually add SPF, DKIM, and DMARC. These names sound technical because they are technical, but the purpose is easy to understand.

    SPF stands for Sender Policy Framework. It tells the world which servers are allowed to send mail for your domain. Think of it as a guest list at the door.

    DKIM stands for DomainKeys Identified Mail. It adds a cryptographic signature to your outgoing mail so receiving servers can check that the message really came from your domain and wasn't altered in transit. It works under the framework defined by the IETF DKIM specifications, which is one of the formal internet standards bodies behind email authentication.

    DMARC stands for Domain-based Message Authentication, Reporting, and Conformance. It tells receiving servers what to do if a message fails SPF or DKIM checks. It also helps domain owners apply a policy against spoofed mail. The standard is documented by the IETF DMARC specification.

    Keep the setup simple and complete

    A lot of failed setups happen because someone adds MX and stops there. That may get mail flowing, but it won't give you the same protection against spoofing or the same deliverability baseline as a full authentication setup.

    If your provider supports standard access, you'll also see references to SMTP. That stands for Simple Mail Transfer Protocol. It's the protocol used to send outgoing mail. IMAP handles reading and syncing. SMTP handles sending.

    Here's a useful rule. Don't guess at DNS values and don't copy examples from random forum posts. Use the exact records your new provider gives you. If one value looks odd, ask support before saving it.

    A quick walkthrough helps if the DNS screen feels unfamiliar.

    Pick a provider your team can actually run

    For a non-technical business owner, setup friction matters. Some providers focus heavily on advanced encryption models such as PGP, or Pretty Good Privacy. PGP can be useful in the right context, but it also introduces key management and workflow complexity that many small teams won't maintain properly.

    A simpler privacy-first service is often the better fit when you want custom domains, standard mail client support, and less administrative overhead. Typewire is one option in that category. It offers custom domain support, migration help, and Canadian hosting under PIPEDA, which can matter if data residency is part of your requirements. The useful outcome is straightforward. You keep control of your domain and mail flow without tying your business inbox to an ad-funded platform.

    Migration support varies by provider

    Privacy-first providers like Typewire usually offer migration help because small business owners rarely have IT departments. That typically means automated import tools, clear DNS guidance, and support that responds to setup questions. Larger platforms (Gmail, Outlook) assume you're either non-technical and won't migrate, or technical enough to handle it yourself. A provider built for small business sits in between: designed for people who want control without complexity.

    Migrating Your Email History and Contacts

    Once the new mailbox exists, you can move your old mail into it. There are two common paths. One is mostly automatic and generally easier. The other is manual and gives you more control when the automatic route doesn't behave.

    A professional man working on a laptop displaying an email inbox, illustrating the process of email migration.

    Automated migration tools

    Many providers offer an import tool that connects to your old mailbox and copies mail into the new one. In practice, you enter the old account credentials, approve access if needed, and let the tool sync folders in the background.

    This approach works well when you have a standard mailbox and want the least manual effort. It's often the right choice for a solo business owner or a small team that doesn't want to manage folders one by one.

    The trade-off is visibility. You usually get less control over odd folder structures, duplicate cleanup, or selective migration. If your old mailbox is messy, the mess may arrive intact.

    Manual IMAP sync with a desktop client

    The manual route uses an email app such as Thunderbird or Apple Mail. You add both the old account and the new account through IMAP, wait for both to sync, then copy or drag folders from one side to the other.

    This takes longer, but it gives you a cleaner hand on the wheel. You can leave junk behind, rename folders, split archives, and verify each folder as it finishes.

    Here's the side-by-side trade-off:

    Method Best for Main advantage Main drawback
    Automated migration tool Most non-technical users Faster and simpler Less control over folder cleanup
    Manual IMAP sync Users who want precision Better control and visibility More hands-on time

    If you want a broader walkthrough of provider switching, our guide on switching email providers with a complete migration guide covers the wider process.

    If your mailbox contains years of history, move the current folders first. Old archives can follow later if time is tight.

    Bring contacts across cleanly

    Import contacts after the mailbox exists but before cutover day. Most providers accept CSV or vCard imports. If your address book is old, open the file first and check for obvious formatting issues, duplicate entries, or missing display names.

    Don't overcomplicate contact migration. You mainly need your active people in place so autocomplete works and your first replies go to the right addresses.

    What usually goes wrong here

    The biggest issue is impatience. Large folders can take time to copy, and desktop clients may appear stuck when they are still syncing. Let the client finish before assuming anything failed.

    The second issue is trying to migrate during business hours without warning. If you rely on your inbox all day, start the copy process before the cutover date so the pressure is lower. Mail history migration and live mail flow are related, but they don't have to happen at the exact same moment.

    Executing the Cutover and Testing

    Cutover is when you point your domain at the new provider for live mail delivery. This is the only time-sensitive part of the project. Everything before this is preparation. Everything after this is verification and cleanup.

    Change the MX records carefully

    Log in to your domain registrar or DNS host and replace the old MX records with the new provider's MX records. Save the changes, then wait. This waiting period is called DNS propagation. In simple terms, internet systems around the world need time to notice the updated records.

    That means some people may reach the new inbox quickly while others may still hit the old one for a while. This is normal. It's one reason we don't shut down the old mailbox immediately.

    Follow a launch sequence

    A short written sequence reduces mistakes:

    1. Confirm the new mailbox works first. Sign in on webmail and, if needed, on your phone and desktop client.

    2. Update the MX records. Double-check that old values are removed if your provider says they should be.

    3. Leave the old account accessible. Don't delete it and don't stop checking it yet.

    4. Send a test from an outside account. Use a different provider if possible.

    5. Send a message out from the new mailbox. Check whether it lands normally and whether replies come back.

    Test more than one path

    A lot of people send one message from their own backup address and call it done. That's not enough. Test inbound and outbound mail with a few different contacts or secondary accounts. If your business uses contact forms, invoicing tools, or website notifications, test those too.

    What you're checking is simple. Does mail arrive? Does it send? Does it land in the inbox instead of spam? Do replies thread properly? Does the From address display the way you expect?

    Treat cutover like opening day. If a system sends email on your behalf, test it before you trust it.

    Communicate during the overlap period

    If you have staff, tell them there may be a short overlap where some messages still arrive at the old inbox. If you're a solo operator, set a reminder to check both mailboxes during the transition period.

    This overlap is annoying, but it's better than missing mail. The smoothest cutovers accept that DNS changes take time and plan for a temporary split instead of pretending everything flips instantly.

    Post-Migration Cleanup and Best Practices

    Once new mail is flowing, the project is mostly done. The final work is about catching stragglers, tightening privacy habits, and deciding when the old account can finally go.

    Keep the old address on a short leash

    Set up forwarding from the old account if the provider allows it, or keep checking it manually for a while if forwarding isn't practical. The point isn't to keep the old inbox forever. It's to catch the people and services you missed during the audit.

    Use this period to update senders one by one. If an old software subscription or supplier still writes to the former address, change it at the source rather than relying on forwarding long term.

    Tell people once, then make the new address stick

    You don't need a dramatic announcement. A short note in your email signature and a direct message to key contacts is usually enough. If you run a business, update your website, invoices, contact page, and any customer support channels at the same time.

    Aliases help here. An email alias is an extra address that delivers to the same mailbox. You can use aliases for billing, support, newsletter signups, or website forms so your main address stays less exposed. If one alias starts attracting spam, you can disable or replace it without rebuilding your whole identity.

    Tighten your long-term privacy habits

    A private email service helps, but it doesn't fix careless habits. Keep these practices in place:

    • Use two-factor authentication: Protect the mailbox and the domain registrar account together.

    • Separate roles with aliases: Keep public-facing addresses away from admin logins.

    • Review forwarding and filters: Old rules can unintentionally send mail to the wrong place.

    • Prefer standard protocols: IMAP and SMTP support reduce lock-in and make future moves easier.

    • Document the setup: Save your provider settings, admin logins, and recovery steps somewhere secure.

    This is also where jurisdiction matters again. If you chose a provider hosting mail in Canada, that can support data residency goals and a clearer compliance story under PIPEDA for some organisations. It won't remove every legal or operational risk, but it does give you more predictable ground than a service spread across foreign infrastructure.

    Know when to delete the old account

    Don't rush this step. Delete the old account only when you've stopped receiving meaningful mail there, updated critical services, and confirmed nobody on your team still depends on it. For some people, that happens quickly. For others, it's worth a longer overlap.

    Our view at Typewire is simple. You should control your email, understand where it lives, and know who profits from running it. As a Canadian company based in Vancouver that operates its own infrastructure, we built around that idea. That doesn't mean every privacy-focused provider is right for every business. It means the trade-offs should be visible, and the service should be easy enough to use properly every day.

    A smooth migration doesn't come from chasing the most complicated setup. It comes from choosing a provider with sane defaults, moving in the right order, and checking every piece before you turn the old one off.


    If you want a private email service that keeps your mail in Canada, supports custom domains, and avoids ads and data mining, take a look at Typewire. We're built for people who want email to stay email, with practical migration support that helps you move without turning the process into an IT project.