Dear Migrate for AODocs users,
We're happy to announce the release of Migrate for AODocs 5.1.
The main focus of this release is the management of uploaders and workspaces (previously called “migration groups”) by administrators.
Improvements
Administration
The administration user interface has been fully revamped and split into four sections:
- Administrators
- Workspaces
- Uploaders
- Users
Learn more: Administrators: Set up and manage Migrate for AODocs
Cloud storage attachments
Migrate for AODocs now supports attachments not only as local files but also stored in Google Cloud storage (your users need access to it).
Migration configuration
You now have choice of where to store your migration data:
- Spreadsheet:
- Advantage: You can add and edit metadata during the migration.
- Disadvantages: You can't manage more than 5 million items of metadata per migration. Also, extraction is a bit slow with large amounts of data to export.
- Cloud Storage:
- Advantages: It’s a hundred times faster than the spreadsheet export, with an unlimited amount of metadata per migration.
- Disadvantage: You can’t edit or add metadata during the migration process.
You now have a “straightforward” option: if you enable the Skip user validation option, the migration process won’t wait for any user interaction from extraction to creation (if the migration is valid).
You now have the option to refresh the AODocs library list. If you just created a library and it doesn’t appear immediately in the user interface, you now have the ability to force the refresh of the AODocs library list.
Gateway
You don’t need to specify your user in the gateway command line anymore, this is driven by the user using the user interface. The spreadsheet creation is now done by the API instead of the gateway to avoid network issues during the initialization of your migration.
Bug fixes
A lot 