Featured image: Four things to consider before a mail migration - Part 3

In Part 3 of our blog series four things to consider before a mail migration, we are talking content security,  timescales and how BCC’s Mail Migration Engine can help.


Content Security

Who gets to see the data while it’s being migrated? A faceless worker in some migration farm will process your mail file if you want to take encrypted messages with you. They have access to your whole mail file including anything encrypted, private and confidential. Content may have to be replicated to migration farms and stored before processing. How secure will that content be? Who will have access?


How long do you need and do you have a deadline? Worried about mass mail migration, all or nothing scenarios and potential bottlenecks in transferring mail?

 Mass push migration – Are you going to attempt to migrate the entire company in one hit? All accounts are migrated at the same time, no issues with co-existence. In large migration projects this can be tricky due to the amount of data to migrate, data to be decrypted / re-encrypted etc.

 Deadline migration – Data has to be migrated by a set cutover date. Migration can push content to the target system with no user interruption. Once the Initial data push has been achieved continuous data sync will keep the target system up to date allowing for a cut over with minimal effort at the designated deadline.

 Long term migration - This scenario is typical of very large graphically dispersed organisations with hundreds of thousands of users. Migrations are run over a long timescale normally months.  Groups of users (departments, physical office locations or company sections) are migrated one group at a time. Each of these groups are seen as mini migration projects themselves.  


How can BCC's Mail Migration Engine help?

Mail Migration Engine (MME) currently supports migrating mail from IBM Domino, IBM Smart Cloud Notes, Microsoft Exchange and Office 365 to Microsoft Exchange and Office 365. Future plans including migration to IBM Domino and to and from Google mail.

Content to be migrated

Starting with planning what and how you tackle a migration is the first step of the migration journey. Due to platforms supported and the flexibility of Mail Migration Engine it is possible to achieve any or a mix of the scenarios covered in part one of the blog post series.


 Encryptions options

With our encryption options it is possible to keep existing encrypted content safe on the source and target systems. MME supports decrypting and re-encrypting content from IBM Domino, MS Exhange and Office 365, including password protected PDFs. As the encyption / decryption processes run at a server task level there is no need for a faceless worker to touch any content, whichever option is chosen.


Content Security

Mail Migration Engine is a server based, what does that mean?

There is no need for client migration farms, no additional user accounts or access is required. A faceless worker in some migration farm has no access to any sensitive data. BCC’s Mail Migration Engine does not require creating any new user IDs for the purpose of migrating the mail data. No direct access rights to the source and target system mailboxes are required. This also means we never store mail data in the Mail Migration Engine, content only ever pass through it — whether migration is performed On-Premises or in the Cloud. 


Time scales

For any of the timescale scenarios described above, Mail Migration can assist. Our continuous syncing technology can ensure source and target systems stay in-sync, minimising co-existence issues. Automation allows for a 24 x 7 sync schedule of all users or groups of users, with the ability to tune for peak times eliminating data bottlenecks. Acquisitions or mergers can mean duplicate account names or email addresses which may need to be addressed. Jobs for account or email name changes can be automated and scheduled.



In summary the experienced BCC Services team can help you get to grips with any size of mail migration project. Run a data migration On-Premises or in the Cloud with no migration farms. Data passes through,  no humans see or touch your data, everything is confidential meaning MME is GDPR compliant.

Get in touch today to learn more about our process and how to get started.

Let's Talk!



Back to all news
Open newsletter modal