Como mudar de Provedor de email.

Question

Just as there are email providers like TASK.COM.BR, is it possible to migrate to an email provider from Microsoft?

Answer 1

Hi  @geomilLTDA-3784

I have noticed that you are using Portuguese in some parts of your question. Please note that this is an en‑us forum. We kindly recommend posting your question in English so that more community members can assist you. Alternatively, you may consider posting in the Brazilian forum if you prefer to use your native language. We sincerely appreciate your understanding. 

Regarding your concerns: 

Yes, it is fully possible to migrate your email from a provider such as TASK.COM.BR to Microsoft’s professional email service. Microsoft hosts business email through Microsoft 365, which supports your existing custom domain. Microsoft provides built-in migration tools, and many companies successfully move from another providers IMAP‑based email systems. 

For email migration steps 

You can follow the standard migration process below. The migration typically takes from a few hours to a couple of days, depending on the data volume. Admin access to your domain’s DNS (via your registrar) and your current email provider is required. 

1.Purchase a Microsoft 365 plan

You could consider to: 

Microsoft 365 Business Basic: Includes 50 GB mailbox storage, Outlook on the web and mobile, Teams, and Exchange Online. 

Exchange Online Plan 1: A cost‑effective option if you only require email services. 

You can sign up at microsoft.com/microsoft-365 or through the Microsoft 365 admin portal.

2.Add and verify your custom domain in Microsoft 365 

Log in to the Microsoft 365 Admin Center.

Go to Settings > Domains > Add domain. 

Enter task.com.br (or your domain) and follow the setup wizard.

Verify ownership by adding a TXT record to your domain’s DNS settings (Microsoft will provide the exact record).

3.Create mailboxes for users 

Go to Admin Center > Users > Active users > Add user.

Assign licenses to each user and create email addresses using your custom domain. 

Mailboxes must be created before migrating data. 

You can refer via: Add users and assign licenses in Microsoft 365

4.Migrate existing emails (usually via IMAP) 

If your current provider supports IMAP (Task typically does): 

Go to Exchange Admin Center > Migration. 

Select Migrate to Exchange Online > IMAP migration. 

Create a CSV file containing users’ email addresses, usernames, and passwords.

Configure the IMAP migration endpoint and start the migration batch. 

Emails and folder structures are migrated automatically. Contacts, calendars, and tasks usually require manual export and import. 

Alternatively, users may import their data using Outlook Desktop (File → Open & Export → Import/Export) or Outlook on the web. 

References: Migrate other types of IMAP mailboxes to Microsoft 365 or Office 365 | Microsoft Learn 

5.Route new email to Microsoft (change MX records) 

Update your domain’s MX records to point to Microsoft (the Admin Center provides the correct values, such as *.mail.protection.outlook.com) 

Remove or lower the priority of Task’s existing MX records 

Note: DNS changes may take 1–48 hours to propagate. During this period, some emails may still be delivered to the old provider, email forwarding can be used as a temporary safeguard. 

6.Set up Outlook and test 

Configure Outlook (Web, Desktop, or Mobile) for users 

Test sending and receiving emails 

Confirm historical emails are accessible 

Once everything is confirmed, the old email service can be canceled. 

Regarding to the advantages of a paid email provider compared to a free email provider 

It is recommended to use paid business email services (such as Microsoft 365) instead of free email solutions for professional use. Paid email services offer custom domain addresses, enterprise‑grade security, full administrative control, and guaranteed uptime through service level agreements (SLAs). They also ensure data ownership, support compliance requirements, and help maintain business continuity as employees join or leave the organization.

Please feel free to correct me if I misunderstood your request. If you have any additional concerns, feel free to comment below. I would be more than happy to assist. 

---

Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 2

I need a specialist.

Answer 3

Qual é passo a passo para migrar provedor de email para Microsoft Outlook. É necessário um especialista? Qual a vantagem de um provedor de email pago por um provedor gratuito?

Answer 4

It is possible to move from a provider such as TASK.COM.BR to Microsoft as the email provider (Microsoft 365/Office 365). The process has three main parts: preparing Microsoft 365, migrating existing email, and redirecting new email to Microsoft.

1. Prepare Microsoft 365 as the new email provider
2. Create or use a Microsoft 365 tenant for the organization.
3. Add and verify the custom domain (for example, @task.com.br) in Microsoft 365:
   • In the Microsoft 365 admin center, go to Settings > Domains.
   • Select Add domain.
   • Enter the domain (for example, task.com.br).
   • Follow the guided steps to prove ownership (usually by adding a TXT record at the DNS host) and complete the setup.
4. Create user accounts and mailboxes:
   • Go to Users > Active users.
   • Create a user for each person who will have email in Microsoft 365.
   • Assign an Exchange Online–included license to each user; without an Exchange license, the domain cannot be used to send/receive email in Microsoft 365.
5. Change users’ email addresses to the custom domain (optional but typical):
   • Still in Users > Active users, open each user.
   • Edit the username and change it from something like ******@tenant.onmicrosoft.com to ******@task.com.br.

This prepares Microsoft 365 to host the same domain that was previously hosted by TASK.COM.BR.

2. Migrate existing email to Microsoft 365

There are several supported migration methods. For a provider like TASK.COM.BR, the most common is IMAP migration.

A. IMAP migration (from most third‑party providers)

1. Preconditions:
   • The current provider must expose the mailboxes via IMAP (most do).
   • All destination mailboxes must already exist in Microsoft 365 (created in step 1).
2. What IMAP migration moves:
   • Email messages in the inbox and other mail folders.
   • It does not migrate contacts, calendar items, or tasks. Those must be moved manually by users (for example, export/import via Outlook) or with other tools.
3. High-level IMAP migration flow:
   • In the Microsoft 365 admin center, use the IMAP migration tool described in “Migrate your IMAP mailboxes to Microsoft 365 or Office 365”.
   • Provide a CSV file listing each source mailbox (on TASK.COM.BR), its credentials, and the corresponding Microsoft 365 mailbox.
   • Start the migration batch; Microsoft 365 connects via IMAP and copies mail into the corresponding Exchange Online mailbox.
   • Let the batch run until the status shows that synchronization is complete.
4. After IMAP migration:
   • The existing mail is copied, but any new messages that still arrive at TASK.COM.BR after the migration will not be automatically moved.
   • Users can manually migrate contacts and calendars using Outlook export/import or other supported methods.

B. Other migration options (if applicable)

If the current system is Exchange Server or another enterprise platform, there are additional options:

• Cutover or staged Exchange migrations (for on‑premises Exchange).
• Third‑party tools (for example, Binary Tree, BitTitan, Quest, Transvault) for complex or large migrations.
• PowerShell-based migrations (cutover, staged, or IMAP) as documented in “How to use PowerShell to migrate email to Microsoft 365”.

These are typically used when there are many users, coexistence requirements, or non‑IMAP sources.

3. Redirect all new email to Microsoft 365

Once mailboxes are created and data is migrated, the domain’s DNS must be changed so that all new email goes directly to Microsoft 365.

1. Understand MX records and TTL:
   • Email delivery is controlled by the MX (mail exchanger) record in public DNS.
   • Other organizations cache the MX record according to its TTL (time-to-live). If the MX is changed before the TTL expires, some systems will still send to the old server until their cache refreshes.
2. Optional: Lower the TTL before the final cutover:
   • On the DNS host for task.com.br, locate the MX record(s).
   • Reduce the TTL to a short value such as 3,600 seconds (1 hour) or less, as recommended in “Migrate other types of IMAP mailboxes to Microsoft 365 or Office 365”.
   • Wait at least as long as the old TTL so that external systems start using the shorter TTL.
3. Change the MX record to Microsoft 365:
   • In the DNS zone for task.com.br, edit the MX record to match the values provided by Microsoft 365 (shown in the Domains setup in the admin center).
   • If there are multiple MX records, update or remove the ones pointing to the old provider so that Microsoft 365 is the active destination.
4. Propagation and verification:
   • It can take up to 72 hours for all external systems to recognize the new MX record, as described in the cutover migration guidance.
   • During this time, some email may still go to the old provider until caches expire; after propagation, all new email will arrive in Microsoft 365 mailboxes.
5. After propagation:
   • Confirm that users are receiving new email only in Microsoft 365.
   • When satisfied that no important mail is still going to the old system, the old email service at TASK.COM.BR can be decommissioned.
6. User-driven imports (alternative or complement)

Instead of (or in addition to) centralized IMAP migration, users can:

• Export email, contacts, and calendars from their old accounts (for example, to PST files using Outlook).
• Import them into their Microsoft 365 mailboxes using the “Migrate email and contacts to Microsoft 365 or Office 365” guidance.

This is often used in smaller environments or when users prefer to control their own data migration.

5. Choosing the best path

• For a typical small or medium business moving from a third‑party IMAP provider like TASK.COM.BR:
  • Add and verify the domain in Microsoft 365.
  • Create users and assign Exchange Online licenses.
  • Use IMAP migration to copy mail.
  • Lower MX TTL, then change MX to Microsoft 365.
• For larger or more complex environments, review “Decide on a migration path” and consider FastTrack or third‑party migration tools.

---

References:

• Ways to migrate multiple email accounts to Microsoft 365 or Office 365
• Migrate email from another IMAP-enabled email system
• Plan for third-party email coexistence with Microsoft 365 or Office 365 and Microsoft Entra ID
• Migrate other types of IMAP mailboxes to Microsoft 365 or Office 365
• Migrate email to Exchange Online using the Exchange cutover method
• Change your Microsoft 365 email address to use your custom domain
• How to use PowerShell to migrate email to Microsoft 365