Technical Description of Service
If you also want to migrate groupware data, please note the Technical Description of the Groupware Migration Service instead of this document.


  • A recent Internet browser with JavaScript support is required for the usage of the audriga email migration service.
  • The email migration service can be used to migrate emails or to backup one or more email accounts, that can be accessed from a server.
  • All directly supported source and destination providers are listed at
  • The user may manually configure IMAP- or POP3-compliant servers including port number. The audriga migration service requires that the IMAP- or POP3-server complies with the respective standard completly and without errors. To allow for a quick migration, the server needs to have a 10 MBit internet connection at least. However, since we are not able to do regular quality checks on manually configured servers, we can not completely gurantee that the migration service will work.
  • For operational reasons, migrations are limited to a maximum of 50 mailboxes and 100 GB of data. A single mailbox may not exceed 10 GB of data. Please contact us in advance, if you want to migrate larger data volumes.
  • For operational reasons, we do not migrated emails larger than 64 MB by default. Please contact us in advance if you would like to migrate larger emails.
  • So called "shared folders" will not be migrated.


  • Connections from the audriga migration service to source and destination providers are encrypted by default, using SSL and STARTTLS. Only if either the source or destination provider does not support encrypted connections, our system will fall back to unencrypted connections.
  • During the migration process, emails will be copied from the source to the destination provider. No changes are made in the destination account.
  • In the destination account, folders and subfolders will be created according to the folder hierarchy in the source account.
  • Some destination providers restrict the creation of folders in a way (e.g., restrictions concerning the depth of folder hiearchy or folder names). Folders from the source accounts that can not be mapped to the destination account will be omitted. The user will be informed if this happens.
  • Emails will be copied from the source account to the destination account including attachments.
  • If supported by the destination provider, flag of an email (e.g., read, unread, important) will be preserved
  • If an identical email is contained multiple times in a folder, it will be migrated to the destination account only once. An email is also categorized as a duplicated and will not be migrated, if an identical email already exists in the destination account.
  • If an email exceeds the data volume limitation of the destination provider, it will not be migrated. The user will be informed if this happens.