Migrate for AODocs is a tool that allows you to migrate files and folders into your AODocs libraries.
This article contains a checklist of what you need to set up before you can use Migrate for AODocs. It also provides some general recommendations.
Automatically generated table of contents
What does the AODocs Support team do so I can get started?
Before you use Migrate for AODocs, the AODocs Support team will:
- configure your domains in Migrate for AODocs on which you want to run advanced migrations
Note: All your domains are available for quick migrations.
- enable your Migrate for AODocs licences
- add at least one Migrate for AODocs administrator
– The Migrate for AODocs Support team can add as many domains as you need.
– Migrate for AODocs administrators can add other administrators.
Any problems? Contact the Migrate for AODocs Support team by email at email@example.com.
What do I need to do before I get started with Migrate for AODocs?
Important: The general prerequisites are mandatory.
Check that you have one or more standard professional user accounts, called migration accounts, on your AODocs domain. Migration accounts will be used to perform migrations.
If you're using Google Drive libraries, as a google Workspace admin, create one or more uploader accounts on your Google domain (recommended five per Migrate for AODocs workspace).
In Migrate for AODocs:
- add the uploader accounts (if using)
- assign the migration accounts that will perform migrations to the appropriate Migrate for AODocs workspaces
- assign uploader accounts to the workspaces used by the migration account
Allowlist the following URLs on your network:
- https://aodocs.altirnao.com (for the US instance) or
https://eu.aodocs.app (for the EU instance) or
https://[instance].aodocs.app (for dedicated instances)
- https://migration.aodocs.com (for the US instance)
or https://migration.eu.aodocs.app (for the EU instance)
or https://migration.[instance].aodocs.app (for dedicated instances)
Learn more: What are AODocs instances?
In addition to the URLs listed above, the Gateway also requires the following URLs to be allowlisted on your network:
To run migrations using Gateway, users must:
- install Gateway
- install Java – learn about which version
- have write access to their AppData folder (on Windows) required to store technical information such as credentials and Sharepoint cached results
- have write access to the folder where the command line runs, to be able to write logs
Your network must have:
- a valid public certificate if you're running migrations from Sharepoint
- Virtual Private Network (VPN) enabled, if any
- No proxy included in the browser (Gateway runs using the command line)
Multiple users should never use the same workspace when using Gateway.
Gateway processes the pending migrations of the workspace. This means that if more than one instances of Gateway are running on the same workspace for different users, this will pick the migrations of the other user.
- one user can run two migrations that use Gateway (such as CSV and Lotus Notes)
- two users, each running a migration that uses Gateway must run their migrations in separate workspaces
Do not exceed 100,000 documents per migration.
Try to split the source data you intend to migrate into specific business cases:
- We recommend migrating a large source dataset into multiple libraries.
- To optimize the upload stage (learn more: What is Migrate for AODocs?) we recommend using five uploader accounts per workspace; you must use at least one and a maximum of ten per workspace.
- Don't share uploader accounts across workspaces, as this consumes the same quota multiplied by the number of times they're shared.
- Don't run migrations containing more than 10 million values in total.
In the data sheet (or CSV), name your headers with strictly distinct values (case insensitive).
- Avoid retrying a migration that is running without a good reason to do so.
- Do not repeatedly click the Next stage button if it doesn't respond instantly. If it seems “stuck”, refresh the page before clicking again to be sure the problem isn’t due to a slow network.