Migrate for AODocs is a tool that allows you to migrate files and folders into your AODocs libraries.
– Migrate for AODocs is currently available for our service teams only. For EAP access, contact:
– To activate the batch migration feature on your domain, contact your account manager or or reach out to us at firstname.lastname@example.org.
If the batch migration feature is activated on your domain, Migrate for AODocs administrators can configure and run batch migrations.
This article describes how to configure and run batch migrations.
|What are batch migrations and how do they work?|
|Prepare your batch migration spreadsheet|
|Create and run batch migrations|
What are batch migrations and how do they work?
A batch is a set of up to 1000 migrations of the same type that you run in one go. Each migration can migrate up to 100,000 documents.
Learn more about the different types of migration available.
Each migration in a batch must have a name that is unique within the batch.
Prepare your batch migration spreadsheet
You can create your batch migration spreadsheet from scratch and fill it in manually. In this case, create a blank Google spreadsheet. Learn more about how to fill it in: The batch migration spreadsheet.
Alternatively, to minimize input errors, you can generate a draft batch migration spreadsheet containing a selection of columns according to the options you choose when you set up the draft. You can then edit the spreadsheet according to your requirements.
2. Press the Batch tab.
3. Press Generate a new draft.
4. Enter a name for your batch migration.
Note: If you don't enter a name, the name of your batch migration spreadsheet is used as the migration name.
5. Define the type of migration.
Note: All migrations in a batch must be of the same type.
6. Select one or both checkboxes:
- Use existing libraries – your draft spreadsheet will have a libraryId column
- Create new libraries – your draft spreadsheet will have libraryName and libraryType columns
Note: You must select at least one of the above checkboxes.
7. Select neither, one or both checkboxes:
- Use custom binding – your draft spreadsheet will have a customBinding sheet
- Use custom mapping – your draft spreadsheet will have customMapping sheet
8. Press Create. A spreadsheet is created and saved to your My Drive.
9. Open the spreadsheet.
The example below shows the spreadsheet that is created if you select the options shown in the screen above.
10. Fill in the batch migration spreadsheet.
When you've finished entering data into your spreadsheet, you're ready to create and run your batch migration.
Create and run batch migrations
1. Press the Batch tab. The list of all batches you created are listed.
2. You can:
- press Start from existing spreadsheet then select batch migration spreadsheet you have prepared manually from Google Drive
- press Start next to the draft batch migration spreadsheet you created and filled in
When you start to create your batch migration:
- It is added to your list of batch migrations in the top panel. If you created it from a draft, the draft remains in the Drafts list until all migrations in the batch are completed.
The Status, Overall progress, Migrations created and Libraries created columns let you monitor the overall progress of your batch creation.
- The report sheet is added to your batch migration spreadsheet. Use the report sheet to monitor the progress of the creation of your batch in more detail.
Important: The data and config sheets in your batch migration spreadsheet are locked when you start to create your batch migration. Never try to edit the data or config sheets while your migrations are being created.
You can refresh the report sheet and open the batch migration spreadsheet from the list of batches.
If the value in the straightfoward column for migrations in your batch is:
- TRUE: when a migration in the batch is created, it starts to run – you can monitor their progress in the Running tab
- FALSE: the migration is created but pauses at the upload stage – you can edit the migration spreadsheet and then confirm manually for the individual migration to proceed