Process for Splitting Company: Splitting the Archive

Problem

A company is splitting into Company A and Company B and wants their archive to be split into Company A and Company B archive.

Solution

1. Setting up Company B in the archive:
   Provide Company B's domains and request for a new customer account, Journaling address and system admin credential
   1. Set up CloudLink using the new system admin credential to synchronize Company B users
      1. Important step to create users accounts and aliases for mail assignment purposes
   2. Set up Journaling for Company B with the Journaling address provided
      1. Confirm archiving in Company B's archive
   3. Request removal of Company B's domains from Company A's archive account
2. Transferring the Legacy Mail into Company B:
   Run an export on the saved search(es) for Company B's mails in Company A's archive
   1. Perform discovery search and create tags for Company B mails in company A's archive
      1.  The search limit is 200,000 mails - create multiple tags & searches if required
      2. (optional *) Create tags so we can remove Company B mails from the Company A archive, if required
   2. Provide us the batch id & passwords for your exports
   3. We will create you a data management case to import Company A's archive mails into Company B
   4. Confirm legacy Company B mails are now in the Company B archive
      1. * If required, Our operations team can run a retention deletion on the tags you provide to remove Company B mails from Company A's archive

Assumptions to make:

• Company B is totally separate (own Exchange and AD) - If Company B is going to share resources with Company A then please contact us before proceeding
• Company B's resources are compatible with our service, please check our compatibility guide for more info
• In cases where Company A and Company B share domains, it is ok to have the same domains on two archive accounts but the set primary domain must be unique
• In cases where a Company B user account is created and they exist as a user of Company A the username needs to be different. A username in one archive cannot match a username of another - again, this would be avoided if the primary domains are different.

Please make your TAM / Client Support aware of any such change as this

Contact support in the first instance if you have any questions