How to free your email from the clutches of Google and Microsoft: A practical migration guide

On October 29, 2026, the discussion regarding digital sovereignty reached a new practical level: migrating personal and corporate email accounts out of the closed ecosystems of Google (Gmail) and Microsoft (Outlook). The movement, dubbed "degoogle" by enthusiasts, is gaining traction as users seek to regain control over their data and communications. The transition requires abandoning the convenience of "big tech" free forms in favor of purchasing a custom domain and contracting independent hosting services, such as Purelymail and Migadu.

The technical framework for this change has existed since the dawn of the internet. Email is, in its essence, a decentralized protocol, designed so that different providers can talk to each other. However, the hegemony of trillion-dollar companies has packaged domain and hosting infrastructure into solutions invisible to the user, creating a strong "lock-in." Breaking this cycle involves taking over the management of DNS pointers and using local clients—tools that require a learning curve but guarantee definitive ownership of your electronic address.

Context and background: The illusion of free services and the closed ecosystem

In the recent past, the mass adoption of Gmail and Hotmail/Outlook accounts occurred due to their free nature and ease of configuration. The business model tied to this convenience is based on scanning data for targeted advertising and creating ecosystems that make it difficult for users to leave. Transition alternatives, such as Apple's iCloud+, have proven to be limited. Users who migrated to Apple's service faced costs starting at R$ 5.90 per month for a mere 50 GB of storage, in addition to technical restrictions, such as distinct addresses falling into the same inbox, proving that switching from one large corporation to another does not solve the structural problem of dependency.

Centralization affects how the internet operates. When a user employs an address ending in "@gmail.com," they do not own that digital identity. Google holds ownership of the address and the keys to the vault, allowing them to revoke access unilaterally. This structural risk has led technologists to recommend registering custom domains associated with providers focused strictly on email hosting, reclaiming the network's decentralized essence.

Technical viability and costs involved

Digital independence has a price and requires manual configuration. The first step is to register a domain. In Brazil, the process is administered by registro.br, where a domain ending in ".br" has a fixed cost of R$ 40 per year. With the domain in hand, the user needs to link this address to an email hosting provider through the configuration of DNS records—codes that translate the site name to the servers responsible for receiving and sending messages.

Practical tests conducted in the second half of October 2026 with independent providers reveal a clear contrast compared to the Silicon Valley giants. Two options stand out:

• Purelymail: Charges a flat fee of US$ 10 per month (approximately R$ 55) for unlimited inboxes. It is an aggressive policy compared to traditional providers that charge "per seat" or per additional user.
• Migadu: Offers the "Micro" entry-level plan for US$ 19 per year (about R$ 100). The Swiss company focuses on stability and boasts an "anti-scalability" philosophy, publicly declaring that it does not seek money from investors or resources driven by Artificial Intelligence, prioritizing serving a restricted base of users reliably.

The file transfer process between providers is facilitated by the IMAP protocol. Free tools like Imapsync allow you to plug in the credentials of the old provider (like iCloud+) and the new one, performing a mirrored copy of thousands of messages in the background.

Practical experience: Performance limits and protocols

The migration is not without friction. During the Purelymail provider test, the transport of a historical collection of over 70,000 messages hit severe bottlenecks. For users with large volumes of data (the so-called "dead archive"), low-cost providers may suffer processing restrictions during massive imports.

Another critical point is calendar and contact management. Outside the Google/Microsoft ecosystem, synchronization depends on the standard CalDAV (for calendars) and CardDAV (for contacts) protocols. Purelymail demonstrated failures in the implementation of native CalDAV calendar invitations, requiring the installation of unofficial parallel systems from GitHub (Purelymail Calendar)—an unacceptable patch for users who rely on normal corporate workflows.

The failure forced a second migration, this time to Migadu, which proved to support CalDAV invitations natively. To fill gaps in webmail (since Migadu's webmail is simple and does not manage web calendars, unlike the Roundcube used by Purelymail), the adoption of a robust desktop email client, such as Thunderbird, became mandatory. Thunderbird replaced the system's native apps (Mail, Calendar, and Reminders), consolidating email, .ics files (calendar), and .vfc files (contacts) into a single open-source interface, even allowing local storage of old emails to save quota on the cloud provider.

Impact for the sector, users, and the Latin American market

For corporate users and independent professionals in Latin America, the paradigm shift carries long-term financial and technical governance advantages. The cost of maintaining a Google Workspace or Microsoft 365 business plan, priced in dollars and scaled by employee, is substantial for small Brazilian businesses. Paying a fixed cost of R$ 55 per month (Purelymail) for infinite inboxes under a custom domain democratizes the professional identity of small studios and agencies.

For "big techs," the immediate impact is mitigated by their size, but the movement strengthens the parallel economy of free software providers. By losing their "lock-in," Google and Microsoft lose exclusivity in collecting metadata from the interpersonal communications of these user segments—data that trains their corporate artificial intelligence models.

The real obstacle in the Latin American market is digital literacy. Configuring SPF, DKIM, and DMARC keys within a provider's DNS panel (an essential step so that email does not fall into others' spam boxes) is an insurmountable technical barrier for the average user. The need for specialized support opens a window of opportunity for IT service providers who perform this "turnkey" migration for small companies.

What is still unknown

• Scalability in critical technical support: It has not been proven how ultra-light providers (like Migadu, which operates with minimal teams) can respond to targeted DDoS attacks or severe cybersecurity incidents requiring immediate contingency.
• Hidden fair-use limits: Plans like Purelymail's (unlimited inboxes for R$ 55/month) depend on "common" usage to balance the server bill. There is no exact transparency on what the cutoff line is (in gigabytes transferred or disk storage) that triggers extra charges to the user.
• Deliverability in hegemonic providers: It is uncertain whether, in the long term, automatic spam detection algorithms from Gmail and Outlook will apply silent penalties to traffic from IPs originating from small and decentralized providers.

What to expect next

The growth of the privacy niche will continue to drive the rescue of local email clients like Thunderbird. Expect updates focused on interface design by open-source foundations to attract young audiences who have never used anything other than webmail.

Independent providers should focus on simplified integration with domain registrars (such as partnerships that automate DNS configuration with a single click), eliminating the main bottleneck of technical adoption. In the long term, the migration will be accompanied by stricter local backup policies, as users understand that leaving data exclusively in the cloud transfers, rather than eliminates, the single point of failure.

Frequently Asked Questions

1. Is it possible to keep my @gmail.com address with an independent provider? No. To use an independent provider, it is mandatory to have your own custom domain (e.g., contact@your-name.com). The @gmail.com address belongs inalienably to Google's infrastructure.

2. Will I lose my old emails when canceling the original provider? If you use tools like Imapsync before canceling the old account, all your historical emails, organized in the same folders, will be safely transferred to the new provider's inbox.

3. What are the DNS records required to host email? They are configuration parameters that must be pasted into the panel where you bought your domain (like registro.br). They indicate to the global internet which servers are authorized to send and receive emails on behalf of your personal address, ensuring that your messages arrive at their destination in an authenticated manner.