FAQ: FirstClass to Office365 Migration Services
What message attributes are included for converted content?
The migration process captures the following message fields:
Is there any limit to the number of messages that can be migrated?
There is no limit to the number of messages that can be migrated.
Is there any limit to the size of an account that can be migrated?
There is no limit to the size of an account that can be migrated.
Is there any limit to the size of messages that can be migrated?
We are able to migrate messages up to 25MB. Any messages larger than this will be skipped during the migration process.
Does the migration capture both inbound and outbound mail?
Does the migration capture mail filed in folders?
Does fcExport capture mail filed in nested folders?
In preparation for the migration process we run a process to "flatten" the folder structure. This ensures that all mail gets migrated, even for folders originally stored several layers down. For example, suppose you have a mailbox with the following structure:
Prior to migration the FirstClass folders would be adjusted to:
The "flat" folder structure is what gets created within O365
Does the migration process capture the Internet address associated with FirstClass user names?
Yes, so long as the user account exists at the time of migration. We use the Internet address assigned on the Aliases field of the User Information Form, allowing your exported messages in O365 to show Internet Addresses for FirstClass users.
How quickly does mail get migrated?
Exact performance varies depending on account size, FirstClass hardware capacity and configuration. In most environments we can migrate 100-200 accounts per day; sometimes more.
How do you determine the destination account for each user?
As part of the migration process we ask for a mapping of FirstClass userID to the email address of the target O365 account.
Will the export process work against a FirstClass Server running OS X?
Yes. The FCAS and O365 upload components of the migration tools need to be installed to a Windows server, which can connect to a host machine running under OS X, Linux, or Windows. Note that performance against OS X and Linux is slower than in a Windows environment, so timing may need to be considered for large migrations.
How does the mail get into O365? do you need O365 account credentials?
There is some configuration we do up-front using an admin-level domain account in O365. This allows us to configure the O365 Import API and Microsoft's Azure tool for uploading content. There's no need to share end-user credentials on either the FirstClass or the O365 side of things.
Please note that at present, Microsoft's tool to upload content is technically in beta. Microsoft has made this available at no charge, and we have used it successfully for many migrations. Microsoft does reserve the right to potentially charge for their tool at some later date, or to change or remove the tool.
Do you have to provide the migration as a service, or can we just purchase the tool and do the migration ourselves?
We strongly recommend mail migration as a service rather than just providing the tool (although we can consider that if needed). The reason is that the migration of mail is a one-time activity for you. We've done this a bunch of times and have gotten good at knowing how to avoid pitfalls and doing the migration as efficiently as possible. By providing this as a migration service we're able to significantly reduce your frustration and time, so you can focus on other aspects of your conversion.
Can you migrate conferences?
Yes, we can export messages from conferences and map these to user accounts in O365 for import. Note that the migration process will only export messages, not uploaded files or objects of other types.
Can you migrate Contacts?
We can produce a .csv export of Contacts for each user if desired. Contacts are not imported automatically into O365.
Can you migrate Calendars?
We can produce a .csv export of Calendars for each user if desired. Calendars are not imported automatically into O365.
How well does the migration process work with UTF-8 content in FirstClass?
Extended 8-bit characters work just fine in both message subjects and bodies. 32-bit characters come through fine in bodies, but are not supported in subject lines or for folder names. Extended characters in subject lines or folder names are omitted in the exported content, or converted to similar ASCII characters.