Migrate for AODocs is a tool that allows you to migrate files and folders into your AODocs libraries.
Learn more: AODocs overview: Choose an AODocs library
With Migrate for AODocs, you can:
- preview the file and folder structure before running the migration
- configure your file and folder data before creating them as AODocs documents and folders
- define the structure of your migrated files before creating them in AODocs
Important: Migrate for AODocs is currently available for our service teams only. For EAP access, contact email@example.com.
|Where can you migrate from with Migrate for AODocs?|
|What is the Migrate for AODocs process?|
|Migrate for AODocs: Basic definitions|
|Extraction and migration spreadsheets|
Where can you migrate from with Migrate for AODocs?
You can migrate data from:
- File servers
- Google Drive
- Google spreadsheets
- CSV files
- Lotus Notes
Learn more: Run your migrations.
What is the Migrate for AODocs process?
The Migrate for AODocs migration process has six stages:
1. Analysis: You can generate a preview of the migration spreadsheet. This lets you analyse the data before the extraction. Learn more: Basic definitions: migration spreadsheets.
2. Extraction: Migrate for AODocs extracts file data and fills in the migration spreadsheet.
3. Upload: Migrate for AODocs completes the extraction and:
- uploads data into the Google Drive migration accounts
- transfers ownership to the AODocs storage account
Learn more: What is the AODocs storage account?
- gives migrated files a Google Drive file ID
4. Validation: Migrate for AODocs checks that your migration is valid.
5. Setup: You can manually configure fields, categories and folders in the migration spreadsheet. Your changes are applied before the documents are created in AODocs.
5. Creation: Create the AODocs documents and folders with the configured data applied.
Learn more: What is an AODocs document?
6. Report (not currently available)
Migrate for AODocs: basic definitions
Migrate for AODocs users can run migrations using their migration accounts. They don't have access to the administration page.
Administrators can run migrations using their migration accounts.
They also have access to the administration page where they can:
- add and remove Migrate for AODocs administrators – learn more: Manage administrators
- create, delete and rename workspaces
- create and delete uploader accounts and assign them to migration accounts
When you perform actions in Migrate for AODocs (such as create and edit the migration spreadsheet) you use your migration account. This is your standard professional Gmail account.
Uploader accounts are technical accounts used to to run your migrations.
Before you use Migrate for AODocs, your G Suite admin must create one or more standard Google accounts which serve as uploader accounts.
Uploader accounts are used only to upload files into Google Drive because this process may overload the My Drive of your migration account. You mustn’t use your professional accounts to upload documents to Google Drive during the migration process.
Uploader accounts are temporary: when your migration is complete, you can delete them so they no longer consume licenses.
G Suite admins can install the Migrate for AODocs - Uploader management application, which automatically authorizes all uploader accounts on your domain. This avoids having to explicitly grant permissions for each one. Learn more: Create and authorize uploader accounts.
– You can’t use an uploader account for more than one migration at a time.
– You can use up to five uploader accounts for each professional account.
Tip: Typically, for 100 migrations, you may use two different professional accounts, each with five uploader accounts. This lets you run 50 migrations sequentially for each professional account at the same time.
Workspaces allow you to organize your migration process according to your business case. Workspaces can be composed of more than one migration. Migrate for AODocs administrators can create workspaces.
For example: You can create one workspace per geographical location (Paris and London). You can then run two separate migrations for the London workspace: one for your local file structure and one for your SharePoint file structure; and run just one SharePoint migration for the Paris migration because you don’t have any local files to migrate.
Extraction and migration spreadsheets
The migration spreadsheet contains the instructions about how to handle your source data during the migration.
You can generate:
- an extraction spreadsheet, to analyse the details of your source files and extract details about the migration (no migration takes place from the extraction spreadsheet) – learn more: Extract details of your source data and migration setup
- a migration spreadsheet, containing all the instructions that Migrate for AODocs uses to migrate your files to AODocs
When you generate a migration spreadsheet, your migration starts. You can edit the spreadsheet to configure your migration while your files are uploading to the My Drive of your uploader account. You then confirm when you’re ready to create your files in AODocs.
– There’s no difference between the extraction and migration spreadsheets, except that in extraction spreadsheets the attachments tab isn't populated. Other than this, they’re generated in exactly the same way, according to the options you select in the configuration screen.
– You can also create migration spreadsheets from scratch.
Gateway is a tool that runs locally during the extraction and upload phases when running the following migration types:
- File server
- SharePoint on premise
- Lotus Notes
Important: You must install Gateway to run these migration types.
Gateway allows Migrate for AODocs to access the local data that you want to import into AODocs. Migration can take a long time, so you may want to quit Migrate for AODocs and close Chrome. You can leave Gateway running so your migration continues.
Learn more: Install Gateway