-
Written By Khushboo Maurya
-
Updated on November 17th, 2026
Moving a business mailbox looks like a simple job until the first issue arrives: “Where did my 2019 emails go?” or “Why am I not getting new mail?” Most of these problems are predictable. They come from skipped prep work, not from the migration itself.
This guide covers how to migrate Dotster to Office 365 (now known as Microsoft 365). Along with that, we will also cover the limitations that Microsoft’s official documents say.
Dotster accounts now fall under Network Solutions. Network Solutions’ own help pages still list separate settings for customers who bought email from Dotster before the move. That matters because you need the right server name for the migration.
Look at the server settings:
|
Setting |
Value |
|
Incoming IMAP server |
|
|
IMAP port |
143, or 993 with SSL |
|
Outgoing SMTP server |
|
|
SMTP port |
587, or 465 with SSL (try 25 if 587 fails) |
|
Username |
Your full email address |
Some accounts use a domain-based format such as imap.yourdomain.com instead. Confirm yours in the Network Solutions email settings tool before you build anything around it.
Dotster supports IMAP, and Microsoft offers a built-in IMAP migration for exactly this situation. Exchange Online signs in to each source mailbox, walks the folder tree and copies messages into a mailbox that already exists on the Microsoft side.
The process has two halves: the mail copy, and the DNS switch that sends new mail to Microsoft. People often forget the second half.
Microsoft’s IMAP migration overview lists several restrictions. Read these before promising anyone a “full” migration:
This is the most common surprise. Because IMAP migration only touches mail folders, your address book and calendar will not follow. Export them from Dotster webmail separately (usually as CSV or vCard/ICS) and import them into Outlook afterwards. For the contact side, see our guide on migrating contacts to Office 365, which covers the import logic.
Microsoft requires every user to exist in Microsoft 365, with a license assigned, before migration starts. If you also want to keep your custom domain on Microsoft, add it as an accepted domain first, then create the users. Reversing that order is a classic reason batches fail on day one.
The migration batch reads a CSV with exactly three headings, no spaces:
One mailbox per row. The file can hold up to 50,000 rows and be up to 10 MB. A single typo in a heading or address is enough to make rows fail.
IMAP migration needs credentials. If you don’t know a user’s password, you must reset it to one you do know, and tell the user afterwards. Skipping this step leaves you with failed rows and locked-out staff.
The MX record tells the internet where to deliver your mail. Move it before the first sync completes and new messages land in a half-empty mailbox. Move it with a long TTL still in place and some senders keep delivering to the old server for hours.
Microsoft suggests lowering the MX TTL to 3,600 seconds or less before you start. Many migration engineers go lower, such as 300 seconds, in the days before cutover. After you switch, allow up to 72 hours for other mail systems to catch up.
Microsoft’s batch syncs once a day. Their guidance is to let it run at least 72 hours after the MX change before deleting it. If you delete early, any mail still arriving at Dotster stops being copied across, and your users never see it. Confirm everyone is working only in Microsoft 365 first.
Even a clean migration is a copy, not a guarantee. Before you touch anything, take a local backup of the source mailboxes. If you want a manual route, our walkthrough on backing up Outlook emails to a hard drive shows how to keep an offline copy you can restore from.
These steps follow Microsoft’s published process for migrating other types of IMAP mailboxes.
Step 1: Prepare the tenant. In the Microsoft 365 admin center, add and verify your domain, then create users and assign licenses. Note each person’s current mailbox size.
Step 2: Tell your users. Explain what will change, when, & what they must do afterwards (sign in, update the password, set the time zone).
Step 3: Build the CSV. Use the three headings above. Save as CSV.
Step 4: Create the migration endpoint. In the Exchange admin center, go to Migration > Endpoints > Add. Choose IMAP, give the endpoint a unique name, and enter imap.dotster.com as the IMAP server. Microsoft says the default values for the remaining fields work in most cases.
Step 5: Create the migration batch. Go to Migration >> Add migration batch. Choose Migrate to Exchange Online, select IMAP migration, pick your endpoint, upload the CSV, set any filters, then schedule and save.
Step 6: Check the results. Open the batch’s details and review the user status report. Failed rows usually point to a wrong password or a bad address in the CSV.
Step 7: Lower the TTL, then switch the MX record. Do this at whichever provider hosts your DNS. Microsoft’s guide to adding DNS records at any provider covers it.
Step 8: Wait, verify, then delete the batch. Give it at least 72 hours, confirm new mail is arriving in Microsoft 365, then delete the batch.
The native tool is free, but it has real gaps: the 35 MB cap, the item limit, no contacts or calendars, and almost no control when something fails. Skipped items in particular can go unnoticed until someone goes looking for a specific message.
If you’re moving many accounts, very large mailboxes, or mailboxes with big attachments, a dedicated third-party migration utility can transfer mail along with contacts and calendars, and filter by date or folder. Always test any tool on one pilot mailbox first.
Most people don’t think about their email until something goes wrong. A hosting provider shuts down, a company switches to Microsoft 365, or a mailbox fills up and old messages start disappearing. That’s when a reliable way to copy mail out of an account becomes important. The Cigati IMAP Backup Tool is built for this job. It connects to a mailbox over the IMAP protocol and copies the contents somewhere safer, or somewhere new.
To understand how this software migrates data, look at the step-by-step guide for the CIgati IMAP Backup Tool.
Security and who it suitsThe software installs on your own machine, so mail doesn’t pass through a third-party server. Data is encrypted in transit, and passwords aren’t stored. The software is GDPR-friendly, and it is for both small businesses and managed service providers who handle mailbox moves for clients. |
Migrate Dotster to Office 365 rarely fails because of the tool itself. It fails when the groundwork gets rushed: mailboxes not created, passwords unknown, contacts forgotten, or the MX record changed too soon. Take a backup first, respect Microsoft’s size and item limits, and keep the batch running for at least 72 hours after cutover. Hold on to the old Dotster mailboxes until everyone confirms nothing is missing. For larger or messier migrations, a dedicated option like the Cigati IMAP Backup Tool can fill the gaps. Whichever route you pick, test one pilot mailbox before touching the rest.
Ans. Yes, if you stay within Microsoft’s limits (35 MB per email, 500,000 items per mailbox) and verify the results. Items above those limits are skipped, so check the batch report. Also, Cigati IMAP Backup Tool is suitable for large data migration without losing emails.
Ans. It depends on mailbox size and how fast the source server allows connections. After the MX change, allow up to 72 hours for full propagation.
Ans. You need either each mailbox password or admin-level access if the source supports it. If you don’t have them, reset the passwords first.
About The Author:
Khushboo Maurya is a digital content and SEO professional focused on creating useful, search-friendly content that connects with the right audience. She specializes in content optimization, website growth, and practical SEO strategies that improve visibility, engagement, and organic reach.
Related Post