Documentation

# iManage

Copy the Files from the \Plugins\Migrate\iManage directory.

Start the migrate tool, a new tab is visible. Click on ... button to create or edit an iManage configuration. The configuration is stored in the \Config\iManage directory.

The plugin does not detect renamed, moved and deleted files and folders. Users should not rename, move or delete files and folders when the migrations has been started.

# iManage Configuration

  • Client / Matter custom table

By default the custom1 table is used for the Client Information and the custom2 table is used for the Matter Information. This can be overridden by specifying the correct custom table number in the setting CustomClientTableNumber and the CustomMaterTableNumber. (valid numbers 1..12 or 29..31)

  • ClientMatterSeparator

Optionally specify a character to specify the combination of a clientcode and mattercode. Should only be used when the matterscodes in iManager are not unique. To be used when specifying one or matters as a source when starting the migration.

  • CombineClientAndMatterCodeToMatterCode

If a character is specified the clientcode and mattercode are merge to a single mattercode using this character when searching for the matter in SharePoint. The combined value should exist as a mattercode in SharePoint.

  • Contenttypes

The class and subclass can be mapped to a contenttype in sharepont. Specify one or more items using the following syntax:

<C_ALIAS>.<SUBCLASS_ALIAS>=ContentType
<SUBCLASS_ALIAS>=ContentType
<C_ALIAS>=ContentType

If a match is found in the above order, that contenttype is used. If no match is found the default content type from the doclib is used.

It's also possible to specify an external text filename, use the extension .txt. Copy the content to a text file and specify a the file path relative to the installation directory in the setting.

  • Users/Groups

The username and groupname can be converted into a sharepoint username/group. Specify the loginname or groupname and the new sharepoint name in the following format. Check if the groups in iManage are not linked to Entra/Active Directory Distribution Groups. Distribution groups are not supported in SharePoint.

<USERNAME>=<Sharepoint username>
<GROUP>=<Sharepoint/Windows AD group>

Optionally use the ReplaceUserGroupNames setting in the Sharepoint config, section Settings. If that mapping contains an empty mapping with a default username, that username is used when the user is not found in Sharepoint.

It's also possible to specify an external text filename, use the extension .txt. Copy the content to a text file and specify a the file path relative to the installation directory in the setting.

  • TargetFolders

See TargetFolder Settings

  • ImportDocumentPermissions

Custom document security is migrated (when security is different from folder). This can be disabled via the setting "import document permissions" = false. The author and/or operator are NEVER added to the permissions with full control. Author and Operator always have full control in iManage without having explicit permissions on the document. If necessary use the DumpDocSecurity and manually import the author/owner.

  • ImportDocumentUseFileEditWhenColumn

If enabled the (new) column FILEDITWHEN is used to also check if the file has been changed/updated in iManage. If changed, the file is re-uploaded to SharePoint

  • ImportDocumentIgnoreProfileChanges

If enabled the column EDITPROFILEWHEN is NOT used to check if the file has been changed/updated in iManage. This could be relevant if a lot of (batch) default meta-data updates have been executed (like updating matternames).

Workspace and Folder permissions are NOT migrated! The dump file contains the custom security on workspaces and folders. This sheet can be optionally used to import via "PermissionSet" import in the monitor directory of the site provisioning tool.

FolderPermissionPublicGroupName / FolderPermissionViewGroupName
Folders can have the default Permissions Public (read/write) or View (read) access. Optionally specify the sharepoint group name that should be used to assign Contribute or Read permissions in sharepoint.

  • DocumentClassToFolders

For documents that are not stored in a workspace or folder, a mapping can be added between a document class /subclass and a folder. Use an empty mapping to configure a default folder.

```text
\<C_ALIAS\>.\<SUBCLASS_ALIAS\>=Folder\
\<SUBCLASS_ALIAS\>= Folder\
\<C_ALIAS\>=Folder\
=Folder default folder if no mapping is found
```

If no default mapping is found, the value of the documentclass /subclass is used as the foldername.

It's also possible to specify an external text filename, use the extension .txt. Copy the content to a text file and specify a the file path relative to the installation directory in the setting.

  • DocumentPropertyToFolders

For documents that are not stored in a workspace or folder, a mapping can be added between a document property and a folder. Use an empty mapping to configure a default folder.

```text
\<AUTHOR\>=Folder\
=Folder default folder if no mapping is found
```

If no default mapping is found, the value of the documentproperty is used as the foldername.

It's also possible to specify an external text filename, use the extension .txt. Copy the content to a text file and specify a the file path relative to the installation directory in the setting.

# Metadata Fieldmapping

By default the values for the metadata from iManage are used in Sharepoint. To update the values use the DynamicFieldMapping in the sharepoint configuration. Use the following fieldnames and map the code to a new value.

  • iManage.DocumentClass
  • iManage.DocumentClassSub
  • iManage.DocumentClassAndSubClass
    combination of class and subclass separated with a dot (.)
  • iManage.Operator
  • iManage.Author
  • iManage.C1ALIAS
  • iManage.C2ALIAS
  • iManage.C3ALIAS (etc. until C16ALIAS)
  • iManage.C29ALIAS
  • iManage.C31ALIAS

If C1DESCRIPTION, C2DESCRIPTION (etc) fields are mapped, the description from iManage is stored and is not replaced via DynamicFieldMapping.

# Import Shortcuts

If enabled only documents that exists in multiple folders are migrated as *.url document, containing a reference to the first migrated document. The oldest entry that is created in a folder is migrated as real document.
The import of shortcuts is NOT logged in the database. When the shortcut import is executed again, existing *.url files will be overwritten. It can create a new URL file if the documentname is updated.

# Dump

Create an excel file containing the following information from iManage:

  • Workspaces
  • Duplicate Workspaces
    Contains a list of workspaces with the same client/mattercode. These workspaces can't be migrated via a client/mattercode, because there's no unique reference. Change iManage to assign or unique mattercode or migrate the workspace via the FolderID to a Matter.
  • Metadata
  • Folders
  • Documents not in folder Returns list of documents that are not stored in a workspace/folder. These files can only be found via search in iManage. (see settings DocumentPropertyToFolders and DocumentClassToFolders)
  • Lookup tables
  • Users and Groups

# Report

Create an excel file containing the information about the import result. Use this report to identify which matters/folders should be reprocessed.

  • Folders, exported documents and errors
  • DocumentErrors, list all documents with an error

# Remove documents during migration

If users have removed documents in iManage after the migration has been run, the documents are not removed in SharePoint. Use the sql script ListRemovedDocumentsDuringMigration to export the list documents to Excel and use the DeleteFiles handler to remove the documents in SharePoint

Last Updated: 3/11/2025, 2:57:59 PM

← iManage Web →