How to Import/Migrate eM Client to Exchange Server? With eM Client to Exchange Migration Tool
You can migrate eM Client emails to Microsoft Exchange Server using Turgs eM Client Converter on Windows. The tool reads eM Client’s local data files and imports them to Exchange Server via admin credentials, preserving folder structure, email headers and attachments.
eM Client is a popular desktop email client for Windows. Exchange Server is Microsoft’s enterprise email platform used by businesses worldwide. Migrating from eM Client to Exchange is a common task when a company moves from individual desktop email management to a centralized Exchange-based infrastructure.
Turgs eM Client Converter automates the migration by reading eM Client’s local email data and importing it directly to Exchange Server.
Why Migrate eM Client to Exchange?
Here are common scenarios where migrating eM Client emails to Exchange makes sense:
- Your company is moving to Microsoft 365 and needs all user email history on Exchange
- You’re consolidating individual eM Client installations to a centralized Exchange Server
- You need Exchange’s advanced features: shared calendars, global address book, enterprise archiving
- Your IT policy requires all email on company-controlled Exchange infrastructure
- You’re onboarding an employee who used eM Client previously and need their email history in Exchange
Exchange Server’s centralized management provides features that individual desktop email clients like eM Client can’t match: message retention policies, eDiscovery, legal hold, and centralized backup. Many organizations find that moving to Exchange as they scale is a natural step.
The migration preserves all email history, so users don’t lose access to years of past correspondence after the move. A typical eM Client data archive might contain 10,000 to 50,000 emails, which the migration tool processes in one batch operation.
Before starting the migration, it’s worth understanding what eM Client stores locally. eM Client uses a SQLite database (emClient folder under AppData) to store all email data. The migration tool reads this database directly, which means Outlook or Exchange don’t need to be installed for the export phase. You only need Exchange connectivity for the import phase.
For enterprise migrations involving dozens of user machines, the tool supports batch mode where you can queue multiple source archives and import them to different Exchange mailboxes in sequence. This significantly reduces the time compared to doing each user individually.
Download Free Trial
Buy Full Version
What You Need
You need Turgs eM Client Converter installed on a Windows machine. You also need admin access to your Exchange Server with sufficient permissions to create mailboxes and import items. The migration can target Exchange Server 2010, 2013, 2016, 2019 and Exchange Online (Microsoft 365).
How to Migrate eM Client to Exchange
Follow these steps to migrate eM Client emails to Exchange Server.
Step 1: Launch the Tool
Install and open Turgs eM Client Converter. The main screen shows the source file selection and mode options.
Step 2: Select eM Client Files
Choose the selection mode: add individual eM Client data files or select an entire folder. The dual mode gives you flexibility to include specific files or process a directory.
Step 3: Choose Exchange as the Destination
In the output format options, select Exchange Server as the migration target. This activates the Exchange configuration fields.
Step 4: Enter Exchange Admin Credentials
Enter your Exchange Server hostname (or Exchange Online URL for Microsoft 365), your Exchange admin credentials, and the target mailbox address. The admin mode option gives you the elevated permissions needed to create items in other users’ mailboxes.
Step 5: Start the Migration
Click Start or Import to begin the migration. The tool processes all selected eM Client data and imports it to the specified Exchange mailbox.
Key Features
Turgs eM Client Converter handles eM Client-to-Exchange migration and more. Key capabilities include:
- Exchange targets supported: Exchange Server 2010 through 2019 and Exchange Online (Microsoft 365)
- Admin mode: Import to any mailbox on Exchange using admin credentials
- Folder structure preserved: Email folders in eM Client are recreated in the Exchange mailbox
- Full data migration: Emails, attachments, sent items, drafts and custom folders all migrate
- Multiple source formats: The tool handles eM Client data and other email formats
- Batch processing: Migrate multiple user archives in one operation
Limitations to Know
Limitations
- Windows only. No Mac version is available.
- Exchange admin credentials are required. The tool cannot import to Exchange without appropriate admin permissions.
- The free trial has a processing limit on the number of emails. The full version removes this restriction.
- Calendar events and contacts in eM Client may need a separate migration step as their data formats differ from email messages.
- Very large eM Client archives with tens of thousands of emails may take 1 to 3 hours to migrate depending on Exchange Server performance and network speed.
- Exchange Online (Microsoft 365) has different connection requirements than on-premises Exchange. Make sure you have the correct endpoint URL for your Microsoft 365 tenant.
Frequently Asked Questions
Can I migrate eM Client to Microsoft 365 (Exchange Online)?
Yes. Turgs eM Client Converter supports Exchange Online as a target. When configuring the Exchange connection, use your Microsoft 365 tenant URL and admin credentials instead of an on-premises Exchange Server address. The migration process is otherwise identical to migrating to an on-premises Exchange Server.
Do I need Exchange admin credentials for the migration?
Yes. Importing email data to an Exchange Server mailbox requires admin-level credentials. You need an account with the ApplicationImpersonation role or similar permissions that allow the tool to import items into other users’ mailboxes. Contact your Exchange administrator if you don’t have these credentials.
What eM Client data types are migrated?
The migration includes emails, attachments, folder structure and email metadata (from, to, subject, date). Calendar items and contacts may require separate handling since they use different data formats. Check the tool’s documentation for the current list of supported data types for Exchange migration.
How are folder names handled during migration?
The tool recreates the eM Client folder structure in the Exchange mailbox. Custom folders you created in eM Client appear as corresponding folders in the Exchange mailbox after migration. Standard folders like Inbox, Sent Items and Drafts map to their Exchange equivalents automatically.
Can I migrate multiple eM Client installations to Exchange in one operation?
Yes. The batch processing capability lets you add data files from multiple users’ eM Client installations and migrate them in one run. Each user’s data is imported to the specified target mailbox. For migrating multiple users to different mailboxes, run the tool separately for each user or configure the target mailbox for each batch.
What’s the difference between migrating to Exchange Server and migrating to Office 365?
Exchange Server is on-premises software run on your own servers. Office 365 (Microsoft 365) hosts Exchange Online in Microsoft’s cloud. Both use the Exchange protocol, but Office 365 requires authentication through Microsoft’s OAuth system. The tool supports both targets. Choose based on where your organization’s email infrastructure is hosted.
