Configure migrations “from scratch” using a Google spreadsheet

Migrate for AODocs is a tool that allows you to migrate files and folders into your AODocs libraries.

Important: Migrate for AODocs is currently available for our service teams only. For EAP access, contact dev-migration@altirnao.com

This article describes how to configure migrations “from scratch” using a Google spreadsheet.


You can run migrations from a blank Google spreadsheet that you fill in from scratch. This feature is usually used to create new documents in AODocs in contexts where you don’t have any source files.

Note: You can’t run an extraction of a manually-created Google spreadsheet.

Generate your migration spreadsheet

1. Access advanced mode and choose to create a  Google Sheets migration. The configuration screen opens.

2. Select:

  • With versions: up to 100 versions are allowed and each row represents a document version 
  • Without versions: versioning is disabled and each row represents a document

3. Select:

  • No attachments
  • Local attachments – you can add files from the following locations: 
      • drive:/[Google Drive ID]
      • gs:/[storage bucket name]/[filename]
      • file:///C:[folder structure]:[filename]
  • Cloud attachments – you can add files from the following locations: 
      • drive:/[Google Drive ID]
      • gs:/[storage bucket name]/[filename]

4. Press Next.

GSimage01.png

5. Fill in the common options for migrations under Define target options.

6. Fill in the common options for migrations under Wrap-up.

7. Press Start Migration

Fill in your migration spreadsheet

1. Open the migration spreadsheet from the card that appears on the Migrate for AODocs screen.

2. If required, enter a different ID for each document you want to create.

Notes:
– IDs are mandatory only if you're using versioning.
– These IDs aren’t used as IDs for your target files. In the context of a “from scratch” migration, they’re used to indicate to Migrate for AODocs to create a different document for each ID.

3. Enter a title for each document.

4. In the data sheet, create or add values to any required columns.

In this example we created:

  • the VERSION column
  • the CLASS_NAME column (because we didn't select a class in the under Define target options)
  • the INITIAL_AUTHOR column
  • columns for properties Contract No. and Amount

Note: If you selected a document class in the configuration screen, columns are created in your spreadsheet for all existing properties in the document class you selected. You can add values as required. Learn more: The data sheet.

image05.png

You can add or edit any of the standard columns in the data sheet:

  • VERSION – enter different version numbers for two or more identical IDs; the format must be X[.Y[.Z]] (where X, Y, Z are integers)
  • VERSION_DESCRIPTION
  • FOLDER
  • RICH_TEXT
  • CREATION_DATE
  • MODIFICATION_DATE
  • UPDATE_AUTHOR
  • ATTACHMENT -– enter the path of a file, for example:
      • local file:
        file:///Users/carolinecharron/Documents/Migration3/AllContracts2019.xls
      • Google Drive file:
        drive:/1veHwMzLy_hgU0iXOJruZdQMuKv_7CEGsPfL6vJAeXdk
      • GCS file:
        gs:/MIGRATION_STORAGE_BUCKET/TrainingPlan.docx
  • [Property names] – enter values in columns corresponding to properties in the document class you selected or create new columns to create new properties.

5. In the binding sheet, set up binding between any columns from the data sheet you want to include in your migration and your AODocs configuration.

6. In the mapping sheet, map the users you entered in the data sheet to users on your AODocs domain.

You're now ready to run your migration.

Was this article helpful? 0 out of 0 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

Comments

0 comments

Please sign in to leave a comment.