How to Migrate Tobit David to Exchange Server & Online – Hosted Exchange Server ?
You can migrate Tobit David emails to Exchange Server using the Turgs Email Backup Tool. It connects to your Tobit David server, reads all mailboxes, and uploads emails directly to Exchange Server or Exchange Online. The tool runs on Windows and preserves folder structure and metadata.
Tobit David is a well-known German groupware and email server solution used primarily by organizations in the DACH region. If your organization is moving off Tobit David and onto Microsoft Exchange, the migration isn’t trivial. Tobit David uses its own proprietary storage format (David File System), and Exchange doesn’t accept that natively.
The backup email tool by Turgs handles this gap. It reads your Tobit David mailboxes directly and uploads everything to Exchange Server or Exchange Online without manual intervention.
Why Migrate Tobit David to Exchange?
Tobit David has a loyal base of users in German-speaking countries, but many organizations are consolidating on Microsoft 365 and Exchange Online for a few key reasons:
- Microsoft 365 integrates with Teams, SharePoint, and the full Microsoft productivity stack
- Exchange Online offers enterprise-grade uptime guarantees and Microsoft-managed security patching
- Exchange is the de facto standard for enterprise email in most industries, making cross-organization collaboration easier
- Tobit David’s hardware and maintenance costs add up compared to cloud-based Exchange subscriptions
The main technical hurdle is the data format difference. Tobit David stores mail in its own proprietary structure that Exchange can’t import directly. You need a tool that acts as a bridge between the two formats.
Migration Tool Overview
The Turgs Email Backup Tool reads Tobit David mailboxes via IMAP/EWS and pushes emails to Exchange Server or Office 365 via the Exchange Web Services API. The tool runs entirely on your Windows machine, so your email data never passes through a third-party server during migration.
The tool supports all versions of Exchange Server from 2010 through 2019 and Exchange Online. It runs on Windows 7 through Windows 11.
One practical advantage: because the tool runs locally, you control the pace of migration. You can pause and resume without losing progress. For organizations migrating during business hours to minimize downtime risk, this is a significant advantage over cloud-based migration services that run on their own schedule.
How to Migrate Tobit David to Exchange
Here’s the complete step-by-step process:
Step 1: Download and launch the tool on a Windows PC with network access to your Tobit David server. Install and open the application.
Step 2: Enter your Tobit David server details. Provide the David server hostname or IP address along with your admin credentials. The tool will connect and load all available mailboxes.
Step 3: Select the folders to migrate. Choose specific mailboxes and folders or select all to migrate everything. The tool shows the folder tree structure from your David server.
Step 4: Set advanced options. Apply date range filters, size filters, or select specific item types like emails, contacts, or calendar items to include in the migration.
Step 5: Choose Exchange Server as your destination. Select Exchange Server from the list of available saving options in the interface.
Step 6: Enter your Exchange Server credentials. Provide the Exchange Server hostname or the Office 365 EWS URL, along with your admin email and password.
Step 7: Click Migrate to start. The tool begins transferring emails from Tobit David to Exchange. A progress bar tracks the migration in real time. For organizations with 10 to 50 mailboxes, expect 1 to 3 hours depending on mailbox sizes and network speed.
When the migration completes, users can log into their Exchange accounts and find all their Tobit David emails, contacts, and calendar items exactly as they were organized on the David server.
Key Features
Direct Tobit David to Exchange transfer. The tool reads from Tobit David and writes directly to Exchange without creating intermediate files. This cuts migration time in half compared to PST-based workarounds.
Preserves folder structure. Your David mailbox hierarchy appears in Exchange exactly as it was on the David server. Users can find their emails immediately after migration without reorganizing anything.
Migrates emails, contacts, and calendars. All three data types migrate in a single pass. You don’t need separate tools or multiple migration runs for different item categories.
Advanced filters for selective migration. Migrate only specific date ranges or folder types. This is especially useful for organizations that want to keep archived older emails on David while migrating only active recent emails to Exchange.
Supports hosted Exchange and Office 365. The tool works with on-premises Exchange Server, hosted Exchange through third-party providers, and Microsoft 365 Exchange Online.
Limitations to Know
Limitations
- The tool runs on Windows only. Mac or Linux machines cannot run the migration software.
- Admin access to both the Tobit David server and the Exchange Server is required. Standard user accounts cannot access all mailboxes without elevated permissions.
- Exchange Web Services (EWS) must be enabled on your Exchange Server or Office 365 tenant for the migration to work.
- The free trial version limits the number of emails migrated per folder. A paid license is required for a complete organizational migration.
- Very large migrations (over 100 GB total) benefit from a dedicated LAN connection. WAN-based migrations will take significantly longer.
- Tobit David-specific features like David.chat conversations and fax data do not migrate to Exchange, as Exchange has no equivalent for those data types.
Frequently Asked Questions
Does the tool work with Tobit David.fx and David 3 versions?
Yes. The tool supports multiple versions of Tobit David including David 3 and later releases. It connects via the server’s IMAP interface, which is available across David versions.
Can I migrate to Office 365 instead of on-premises Exchange?
Yes. Microsoft 365 Exchange Online is a supported destination. Use the EWS URL for your Office 365 tenant in the Exchange Server field when setting up the migration.
Will the Tobit David folder structure be recreated in Exchange?
Yes. The tool recreates your David mailbox folder hierarchy in Exchange. All custom folders, subfolders, and nested folder structures appear intact after migration.
Can I migrate only selected mailboxes instead of everything?
Yes. The tool lets you choose individual mailboxes or specific folders during the setup phase. You can run phased migrations by migrating active users first and archived mailboxes later.
How long does a Tobit David to Exchange migration take?
A 10 GB mailbox migrates in approximately 45 to 90 minutes on a standard business LAN. Larger organizations with 50+ mailboxes should plan for an overnight or weekend migration window to minimize disruption.
Is the migration data secure?
Yes. The tool runs entirely on your local machine and transfers data over an encrypted TLS connection between your David server and Exchange. Your email data does not pass through any third-party servers during migration.
