Migrate for AODocs V10.0 Release notes

Hi Migrate for AODocs users,

We're pleased to announce release 10 of Migrate for AODocs!


What's new?

You can now

Sharepoint 2007

Until now Migrate for AODocs only supported:

  • Sharepoint online
  • Sharepoint 2013
  • Sharepoint 2016

We added the support of:

  • Sharepoint 2010
  • Sharepoint 2007

Like the previously supported versions of Microsoft Sharepoint, you can use date filters, automatically generate your custom properties and import previous versions into AODocs.

The only visual difference is a new option in the Sharepoint migration creation form here:


As Sharepoint 2010 is an on premise application, options are disabled until you activate Gateway.

Google Drive

Entire shared drive

As some of you noticed, the Google Drive picker didn’t allow you to select an entire shared drive – you had to select a folder in it. You can now migrate an entire shared drive. All the shared drives you are a member of are listed next to the Google Drive picker.


This option is available for both Quick and Advanced migrations.

Move and copy

Until now, for migrations containing Google Drive attachments, the attachments were moved. This meant you had to be the owner or an AODocs super administrator to perform the migration.

You can now choose between:

  • moving your attachments
  • moving all files and copying the ones you are not allowed to move
  • copying all your attachments

However, be careful when choosing to copy your attachments, as it generates new attachment links. Whenever it is possible, we strongly recommend sticking with moving attachments.


That option is not available when storing attachments in GCS, as they are necessarily copied.

Additional information:

  • The Copy all files option should only be used for tests or demos.
  • The Copy when moving is not allowed option solves the limitation of document creation based on files outside your domain or migration performed by users who:
      • are not AODocs super administrator
      • do not own all the files

And there's more...

No need to use the API to revert migrations from CREATION to SETUP

Some of you noticed your migration might be in the CREATION stage without having all the configuration prepared in SETUP. You previously needed to use the API to update the migration stage manually.

For migrations in ERROR in CREATION stage, you now have two options:

  • retry the migration to re-perform the migration after fixing the displayed error
  • reset to SETUP stage the migration to re-perform the scaffolding process

Lowercased users

Previously, the names of uploaders and administrators were case sensitive, which meant you could be unauthorized if there was a case mismatch between your user and the one filled in the administration of the domain. That’s not the case anymore!

The API explorer link is back!

For advanced use cases, you sometimes need to access the API explorer of the application. The link is now accessible in the Information menu next to your profile.



Was this article helpful? 1 out of 1 found this helpful
If you didn’t find what you were looking for, don’t hesitate to leave a comment!
Have more questions? Submit a request



Please sign in to leave a comment.