NevTan Mail is secure, ad-free business email for your entire organization, and this guide shows you how to move your entire team to it at once using bulk mailbox import. You will learn the exact steps to prepare your data, format your CSV file, and migrate hundreds of mailboxes without downtime or data loss. By the end, you will have a complete, repeatable process that works for teams of 5 or 500. This method eliminates the tedious task of creating accounts one by one, saving your IT team days of manual work and reducing the risk of human error that comes with repetitive data entry.
Bulk mailbox import lets you create and migrate many email accounts at once using a CSV file. You need your domain verified, a formatted CSV with names and email addresses, and admin access to your current provider. The process takes about 30 minutes for 100 mailboxes, and NevTan Mail's admin panel handles the rest automatically. You can migrate existing mailboxes with full email history or create fresh accounts, and the entire process is designed to work without any downtime for your team.
What You Need Before Starting
Before you begin a bulk mailbox import, you need three things in place. First, you must own the custom domain you plan to use for your email addresses — if you have not set one up yet, start with our guide to business email on your own domain. Second, you need admin access to your current email provider to export your existing data. Third, you need a CSV file that lists every mailbox you want to create. These three prerequisites are non-negotiable, and having them ready before you start will make the entire process significantly smoother.
Your domain must be verified with NevTan Mail before you can import any mailboxes. This involves adding a few DNS records to your domain registrar, which takes about 15 minutes. The verification process confirms that you own the domain and authorizes NevTan Mail to send and receive email on your behalf. It is also where your SPF, DKIM, and DMARC records are established — a step worth understanding properly, since misconfigured domain authentication is the most common reason business email lands in spam. You also need to decide whether you are creating new mailboxes from scratch or migrating existing ones with their historical email data. This decision affects how you prepare your CSV file and what export steps you need to complete with your current provider.
For a migration, you will need to export your current mailboxes using IMAP or a provider-specific export tool. Google Workspace, for example, lets you export user data through their Admin console. Microsoft 365 offers a similar export feature through the Exchange Admin Center. You will also need the passwords or app-specific passwords for each mailbox you plan to migrate. If you have two-factor authentication enabled on your current provider, you will need to generate app-specific passwords for each user, as your standard login credentials will not work for IMAP-based data transfer.
Additionally, you should audit your current mailbox list before exporting. Check for inactive accounts, former employees, and shared mailboxes that may not need to be migrated. This is the perfect time to clean up your email infrastructure and only move the accounts that are actively used. A typical organization finds that 10-15% of their mailboxes are stale or unused, so this audit can save you both time and money during the migration — and it directly affects your final mailbox count, which is what NevTan Mail's pricing is based on.
Step-by-Step Guide
Step 1: Export Your Existing Mailbox Data
The first step in any bulk mailbox import is exporting your current data from your old provider. This includes emails, contacts, and calendar entries for every user you plan to move. Skipping this step or doing it incorrectly is the most common cause of data loss during migration, so take your time and verify everything before proceeding.
Log in to your current email provider's admin console and locate the export or migration tool. For Google Workspace, go to Admin Console > Data Migration. For Microsoft 365, use the Exchange Admin Center. You will need to create a CSV file that maps your old email addresses to your new ones. This mapping file is separate from the CSV you will upload to NevTan Mail, and it ensures that each user's data lands in the correct new mailbox.
Export your data in standard formats like .pst for Outlook or .mbox for other clients. Most providers also offer a direct transfer option that moves data between servers without downloading it to your computer. This is faster and more reliable for large teams, as it eliminates the risk of incomplete downloads and corrupted files. Direct transfer typically uses the IMAP protocol and can move data at speeds of 100-200 MB per hour, depending on your internet connection and the provider's server load. If you are unsure which protocol does what, our breakdown of IMAP vs SMTP vs API explains where each one fits.
💡 Pro Tip: Export a single test mailbox first and verify the data is complete before exporting your entire organization. This catches permission errors early and saves you hours of troubleshooting. Check that the test export includes emails from all folders, not just the inbox, and that attachments are intact. A 15-minute test can prevent a full-day migration failure.
Step 2: Prepare Your CSV File
Your CSV file is the backbone of your bulk mailbox import. It tells NevTan Mail which mailboxes to create and how to configure each one. A well-structured CSV file ensures that every mailbox is created correctly the first time, with no missing information or formatting errors that could cause the import to fail.
Create a CSV file with columns for first name, last name, email address, and password. You can also include optional columns for display name, department, and role. Use a simple text editor or spreadsheet application to create this file, and save it in UTF-8 format to handle special characters correctly. UTF-8 encoding is essential if any of your team members have non-English characters in their names, such as accented letters or non-Latin scripts.
Here is an example of a properly formatted CSV file:
csv
first_name,last_name,email,password
Sarah,Johnson,sarah@yourdomain.com,SecurePass123!
Mike,Chen,mike@yourdomain.com,SecurePass456!
Priya,Patel,priya@yourdomain.com,SecurePass789!Ensure every email address uses your verified custom domain. Do not use personal email addresses like @gmail.com or @yahoo.com. Also, generate strong, unique passwords for each mailbox rather than using a single shared password. A shared password across all mailboxes is a severe security risk, as a single compromised account would give an attacker access to your entire organization's email system — the kind of scenario covered in our guide to email security, phishing protection, and TLS encryption.
💡 Pro Tip: Use a password generator to create unique passwords for each mailbox. Store these in a secure password manager and distribute them to your team after the migration. You can also use a formula in your spreadsheet application to generate random passwords for each row, ensuring that every mailbox has a unique, cryptographically strong credential.
Step 3: Upload Your CSV to NevTan Mail
Once your CSV file is properly formatted and your data is exported, you are ready to upload it to NevTan Mail. Navigate to the admin panel in your NevTan Mail dashboard and locate the "Bulk Import" or "Mailbox Import" section. This is typically found under the "Users" or "Admin" menu, depending on your account configuration. Admin and Super Admin roles control who can access this area — see the full team and admin feature set for how permissions are structured.
Click the upload button and select your CSV file. NevTan Mail will parse the file and display a preview of the mailboxes it will create. Review this preview carefully to ensure that all email addresses are correct and that no rows are missing or duplicated. The preview step is your last chance to catch errors before the import begins, so do not rush through it.
After you confirm the preview, NevTan Mail will begin creating the mailboxes. For 100 mailboxes, this typically takes about 30 minutes. The system will show you a progress bar and provide a summary report when the import is complete. This report lists any mailboxes that failed to create, along with the reason for each failure, so you can fix the issues and retry those specific entries.
Step 4: Migrate the Data
If you are migrating existing mailboxes, you will now need to transfer the data from your old provider to your new NevTan Mail mailboxes. This step runs in the background and does not require your team to stop working. Your users can continue using their old email while the migration runs, and they will only switch over once everything is complete.
NevTan Mail connects to your old provider using the IMAP credentials you provided during the export step. It then copies emails, contacts, and calendar entries from the old mailboxes to the new ones. The migration speed depends on the volume of data and your internet connection, but most teams see completion within 24-48 hours for typical usage patterns.
During the migration, you can monitor progress from the admin panel. You will see a per-user status indicator showing whether each mailbox is pending, in progress, or complete. If any mailbox fails, you can retry it individually without affecting the rest of the migration. This granular control ensures that one problematic mailbox does not hold up your entire team's transition.
Step 5: Verify and Switch Over
Once the migration is complete, you need to verify that everything transferred correctly before switching your team over. Spot-check several mailboxes to confirm that emails, contacts, and calendar entries are all present. Compare the message counts in a few key folders between your old and new systems to ensure nothing was lost in transit.
After verification, update your DNS records to point your domain's MX records to NevTan Mail. This is the final step that routes new incoming email to your new mailboxes. MX record changes typically propagate within 1-2 hours, though it can take up to 24 hours in some cases. Plan your switchover for a low-traffic period, such as a weekend or after business hours, to minimize the impact of any email delivery delays during propagation. Once you are live on the new domain, review our email deliverability best practices to protect your sending reputation from day one.
How Bulk Mailbox Import Works Technically
Bulk mailbox import relies on a combination of standard email protocols and automation to create and populate many mailboxes simultaneously. At its core, the process uses IMAP (Internet Message Access Protocol) for data transfer and a structured data format (CSV) for account configuration. Understanding the technical underpinnings helps you troubleshoot issues and set realistic expectations for your migration timeline.
When you upload your CSV file, NevTan Mail's backend parses each row and generates an API call to create a new mailbox with the specified parameters. These API calls are batched and processed concurrently, which is why the system can create 100 mailboxes in approximately 30 minutes. The batching system also includes error handling that isolates failures, so one invalid email address does not prevent the other 99 from being created successfully.
For data migration, the system establishes an IMAP connection to your old email server using the credentials you provided. IMAP is the industry-standard protocol for email retrieval and synchronization, supported by virtually every email provider including Google Workspace, Microsoft 365, and Zoho. The migration tool then synchronizes folders, messages, and metadata between the two servers. This includes not just the inbox but also sent items, drafts, trash, and any custom folders your team has created.
The entire process is designed to be non-destructive. Your old mailboxes remain untouched throughout the migration, so you always have a fallback if something goes wrong. This is why the process is safe to run without downtime — your team can continue using their current email while the data copies in the background. Only after you verify the migration and update your MX records does the new system become the primary destination for incoming mail.
Explanation
Bulk mailbox import is a sophisticated orchestration of several distinct technical systems working in concert. When you upload a CSV file to NevTan Mail, the backend first validates the file structure against a strict schema. This validation checks for required columns, correct data types, and proper email formatting. If the file contains 500 rows, the system validates all 500 before creating a single mailbox, which prevents partial imports and inconsistent states.
Once validation passes, the system enters the provisioning phase. Each row in your CSV triggers a series of API calls to create the mailbox, set the password, and apply any optional attributes like department or role. These calls are executed in parallel batches of 20-50 mailboxes at a time. This parallelization is what enables the system to create 100 mailboxes in roughly 30 minutes — a sequential process would take 3-4 times longer. The provisioning engine also implements idempotency keys, meaning if a network interruption occurs mid-batch, retrying the operation will not create duplicate mailboxes.
For migrations, the data transfer layer uses IMAP IDLE and folder synchronization to copy messages efficiently. The system first establishes a connection pool to your old server, typically maintaining 5-10 concurrent IMAP connections. Each connection handles a separate mailbox, and the system dynamically allocates connections based on mailbox size. A mailbox with 2 GB of data will receive more bandwidth than one with 200 MB. The transfer engine also performs incremental syncs, checking for new messages every 15 minutes during the migration window. This ensures that emails received after the initial sync are still captured before you switch over your MX records.
The system also tracks transfer metrics in real time. You can see messages per second, bytes transferred, and per-folder completion percentages in the admin dashboard. On average, the system transfers 1,500-3,000 messages per hour per mailbox, depending on message size and server response times. For a team of 50 users with an average mailbox size of 1.5 GB, the full data migration typically completes in 12-18 hours. The system compresses data in transit using TLS 1.3 encryption, and all transferred data is checksum-verified to detect corruption. If a checksum mismatch occurs, the system automatically retries that specific message rather than failing the entire mailbox.
Finally, the verification layer runs post-migration audits. It compares message counts, folder structures, and attachment integrity between source and destination. The audit report shows a per-mailbox score from 0-100%, and any mailbox scoring below 99.5% is flagged for manual review. This level of granular verification is what makes bulk import reliable for organizations with strict compliance requirements. For a wider view of how encryption is applied across a business email platform, see our overview of email encryption for business.
Common Mistakes to Avoid
One of the most common mistakes during bulk mailbox import is using an incorrectly formatted CSV file. Missing headers, extra commas, or unquoted fields with special characters can cause the import to fail or create mailboxes with incorrect information. Always validate your CSV file with a text editor before uploading, and check that every row has the same number of columns.
Another frequent error is attempting to migrate without first verifying your domain. If your domain is not verified with NevTan Mail, the import will fail because the system cannot create mailboxes on an unverified domain. Complete the DNS verification steps before you even start preparing your CSV file to avoid this unnecessary delay.
Many teams also forget to generate app-specific passwords for their old provider when two-factor authentication is enabled. Standard passwords will not work for IMAP connections, and the migration will fail with authentication errors. Generate app-specific passwords for each user before you begin the export step, and store them securely until the migration is complete.
A subtler mistake is switching your MX records before checking your authentication records. New domains and freshly moved domains are scrutinized more heavily by receiving servers, and a gap in SPF or DKIM at the moment of cutover can send your first week of mail straight to junk. Our guide on why emails go to spam and how to fix it covers what to check before and after the switch.
Finally, do not skip the test export. Migrating your entire organization's data without first testing a single mailbox is risky. A permission error or misconfigured export setting could result in incomplete data for every user, and you would not discover the problem until after you have switched over. The 15 minutes it takes to test one mailbox is a small price to pay for the confidence that your full migration will succeed.
How to Choose
Choosing the right approach for your bulk mailbox import depends on several factors that you should evaluate before starting. Use the following criteria to make your decision:
Team size. If you have fewer than 25 mailboxes, you might consider manual creation. For 25-500 mailboxes, bulk import is clearly the better choice. Above 500, you should contact NevTan Mail support for a custom migration plan. Smaller teams weighing the cost of a move should also read our cheap business email guide for startups.
Data volume. Estimate the total size of email data you need to migrate. If your team has less than 50 GB total, a standard IMAP migration works well. For larger volumes, consider a direct server-to-server transfer to avoid bandwidth bottlenecks.
Downtime tolerance. If your team cannot afford any email interruption, choose the non-destructive background migration approach. This lets users keep working on the old system until verification is complete.
Historical data needs. Decide whether you need full email history or just recent messages. Migrating 7 years of email for 200 users takes significantly longer than migrating 1 year. You can configure NevTan Mail to only sync the last 90 days if older data is archived elsewhere.
Security requirements. If your organization handles sensitive data, ensure you generate unique passwords for every mailbox and use app-specific passwords for the source system. Also verify that your migration plan includes encrypted transfer via TLS.
Timeline. Map out your migration window. Account creation for 100 mailboxes takes about 30 minutes, but data migration can take 24-48 hours. Plan your switchover for a weekend or low-traffic period to accommodate DNS propagation.
By scoring yourself against these six criteria, you can determine whether to proceed with self-service bulk import or engage NevTan Mail's team for assisted migration.
Frequently Asked Questions
How long does a bulk mailbox import take? A bulk mailbox import for 100 mailboxes typically takes about 30 minutes for account creation. Data migration runs in the background and usually completes within 24-48 hours, depending on the volume of email data and your internet connection speed. Larger teams with more data should expect longer migration windows.
Can I migrate mailboxes from Google Workspace? Yes, NevTan Mail supports migration from Google Workspace, as well as Yahoo and Zoho, over IMAP. You will need admin access to your Google Workspace account and app-specific passwords for each user if two-factor authentication is enabled. Use the Admin Console's Data Migration tool to export your data. Teams comparing platforms before committing may find our look at why teams are switching to modern webmail useful context.
What CSV format does NevTan Mail require? NevTan Mail requires a CSV file with columns for first name, last name, email address, and password. Optional columns include display name, department, and role. Save the file in UTF-8 format to handle special characters correctly.
Will my team experience downtime during migration? No, the migration is designed to be non-destructive and runs in the background. Your team can continue using their current email while data transfers. Only after you verify the migration and update MX records does incoming mail route to the new system.
What happens if some mailboxes fail to import? NevTan Mail provides a summary report after the import that lists any failed mailboxes along with the reason for each failure. You can fix the issues and retry those specific entries without affecting the mailboxes that were created successfully.
Do I need to keep my old email provider after migration? It is recommended to keep your old provider active for at least 30 days after migration. This gives you a safety net in case you discover missing data or need to reference old records. After 30 days, you can cancel your old subscriptions.
Can I import mailboxes without existing email data? Yes, you can create new mailboxes from scratch without migrating any historical data. Simply prepare your CSV file with the mailbox details and skip the export and data migration steps. This is ideal for new teams or organizations starting fresh.
How do I generate app-specific passwords for migration? For Google Workspace, go to your Google Account settings and select "App passwords" under Security. For Microsoft 365, use the Security & Compliance Center. Generate a unique app password for each mailbox you plan to migrate and store them securely.
Wrapping Up
You now have the complete playbook for bulk mailbox import, from preparing your CSV file to verifying the final switchover. The process is designed to be non-destructive, background-running, and fully monitored, so your team never experiences downtime. Whether you are moving 5 mailboxes or 500, the steps remain the same: verify your domain, export your data, format your CSV, upload, migrate, and verify.
NevTan Mail is the right choice for this migration because it combines strong security with a straightforward admin interface. You get TLS-encrypted connections, guided SPF/DKIM/DMARC setup, and role-based admin controls — all without the advertising and data-selling practices of free consumer email providers. The built-in calendar, tasks, and meetings tools mean your team gets a complete communication suite, not just email. For a full tour of what the platform covers, read what NevTan Mail is and how it works.
If you are also sending contracts or documents that require signatures, explore how NevTan Sign integrates with your new email workflow. And for marketing campaigns after the migration, NevTan Engage lets you reach customers across channels from the same connected suite — just keep transactional and marketing mail properly separated so your migration does not undo your deliverability.
Start your migration today by setting up your custom domain with NevTan Mail, or browse more guides on the NevTan Mail blog.
