Content Mover helps you to move content such as Teams and Channels from M365 to a DMS and automatically sync any changes between M365 and DMS.
Litera Prosperoware CAM Azure Stack utilizes Microsoft Azure services and resources to provide the ability to sync content between multiple Document Management Systems (DMS). On the Azure Stack, CAM Content Mover uses Azure storage blobs as an intermediary when copying content between the supported DMSs.
Note: For information on the Azure Stack Deployment or AWS Stack Deployment, see the relevant links.
CAM Azure Stack requires the deployment of an Azure template into your Azure environment. The template deploys a complete solution that contains multiple resources such as function apps, MySQL instances, BLOB Storages, and others. These resources are provided and hosted by Microsoft Azure in your Azure account to provide you with more control over the Content Mover process.
Major features include:
Moving channels, tabs, and teams from the Teams application to the DMS system from the Matters tab.
Copying channels, tabs, and teams from the Teams application to the DMS system from the Matters tab.
Setting up content mover jobs between systems to occur on a schedule.
Allowing CSV Upload of Jobs to move channels, tabs, or teams from the Teams application to the DMS.
Tip: The file size should be 450MB or less from M365 to NetDocuments in Azure and AWS to sync the contents.
License and Add-on Requirements
The license tier must be Move or higher.
Permissions for Content Mover and its functions can be found here.
Accessing Content Mover Manager
After granting permission, you can access Content Mover Manager to configure the content mover job.
In CAM, navigate to the Administration panel.
Click Content Mover, and the following screen opens
If multiple pages exist, pagination will be displayed at the bottom.
Also, use the filter to filter out the content mover job.
We now support filtering by Created By and Created
Note: If the job is deleted after copying the contents then resubmit the same job again, the new document will be created, however the old document will be lost!
The Database column will display N/A for any system that doesn't contain a cabinet.
M365 to iManage
Office365 Jobs
Allows the user to search the config job, and edit/update the config job. Users can perform the following operations -
Filter - Allows you to filter or search the config job based on the following two options -
Source option - It contains the following field -
System - Select the system from the list.
Repository - Select the repository from the list.
Entity Name - Enter the entity name. We support special characters in the search.
Target Option - It contains the following field
System - Select the system from the list.
Repository - Select the repository from the list.
Entity Name - Enter the entity name. We support special characters in the search.
Click Search to display the result and click Clear to clear the fields
Fields | Description |
|---|---|
MappingId | The job mapping id will display in this Jobs panel for each job. |
Source | Displays all source details. |
Target | Displays all target details. |
Details | Detail contains the following fields -
Note: View Content Mover Logs permission is required to see the Logs menu option. |
Status - Displays the job status of:
Running
Complete
Inactive
Error. If an error happens during an Content Mover process, CAM sends an email notification to the user. The message will look like this:
Actions - Click the Hamburger menu to upload the CSV.
Edit the Content Mover Job
Allows the user to edit/update the job. Users can perform the following operations -
Column | Description |
Enabled | Select value |
From System | Select value from dropdown |
To System | Select value from dropdown |
Current Interval | Displays the current interval |
New Interval: Every |
|
Profile | Enter the following values -
|
Settings | Enter the following values: 
Note: iManage does not allow to import multiple versions of email documents.
Content Mover supports the option to replace shortcuts. Select from either Yes or No. 
Note: Chat and post files are updated on the delta if the file or folder is updated. If not updated, the updated chat will not sync.
Note: If an existing OneNote is added inside a Team, and the Repository isn’t one that is subscribed to, the Job event won’t be triggered until a change is made, or the Repository is subscribed to. You can transfer your contents to iManage by selecting one of the options:
Important: You can view in the iManage, OneNote notebook is stored as a folder with a separate data file for each section. OneNote files have a .one filename extension.
You can transfer your contents to iManage by selecting one of the options: 1. Copy as folder – This allows you to create a folder and then move the contents of that folder.
– This allows you to skip ahead in order to move contents. Skip is set by Default for all Teams to iManage jobs. Important: You can view in the iManage, planner is stored as a folder with a separate data file for each section. Planner files have a .xlsx filename extension.
Note: When documents are copied and synced across DMS systems, review the security of the Access Control List (ACL) as documents are accessible to anyone who has access to the destination folder.
 Important: The option will display for jobs which are configured to Bring as Shortcut for How would you like to sync documents, and if the user has permissions to trigger this action. 3. On the dialog, select between Stop Sync or Continue Sync, and click Yes. 
If Replace shortcut with Continue Sync is selected, Additional Settings can be edited for the job. 
Notes:
Note: Replace Shortcut functionality is currently only supported for iManage. If the target is other than iManage, the Replace Shortcut Action will be hidden.
Users can assign a custom name to a team being copied from Teams into a DMS Workspace / Folder. The parameters can be found on the Creating a Workspace page. Copy to Site (Sharepoint)The Copy to Site has the same steps as Copy As to Teams. The following cases are supported when Copying to a Site:
Warning: CAM will apply the Rule format "@system@_@clientId@-@matterId@" if the Rule format from Copy As is removed after saving. This is a CAM limitation. |
Template Mapping |
Once done with the mapping, the results display in a grid format. |
Azure Communication Settings | Enter the details of the Azure account for email alerts and notifications to be setup on Content Mover.
Options for these settings as a whole are:
|
Click Update to update the added details and click Cancel to close dialog.
Delete the content mover setting
Allows the user to delete the content mover job. Following screen displays -
Enter a reason to perform the delete operation.
Click Delete to remove the config job and click Cancel to close the dialog.
Default Setting
Then go to the Default Settings tab. This tab shows all mapped content mover systems to run jobs off of.
Following screen displays -
Column | Description |
From | Shows the system the content mover is reading from. Always will be Office 365. |
To | Shows the system the content mover will move or copy to. Typically the DMS system. |
Enabled | Displays if the job is enabled or not. |
Bringing Post Files | Shows or hides the post files as per the option chosen by you on the Edit Job Settings screen. |
Source Security Applied | Displays if the job applies the source system security (the system in the from column). |
Sync Interval | The job sync internal (in minutes, hours or days). |
Start Date | The job start date to start on. |
Actions | Allows below actions based on permissions:
|
Adding a New Mapping
Click Add New from the Default Settings tab.
Set if the job will be enabled from the start. If it will be, select Yes.
The “From” system will be auto-populated to Office 365. This cannot be changed.
Select the To System. Currently supported systems are iManage, Office 365, Fileshare, and NetDocuments.
Select the repository if multiple repositories exist on the external system.
Set up a new job internally in the New Interval. Set the period in Every, select the time measure (minutes, hours, or days), and set the starting period date (today, in the future).
Add Profile of the job next:
First set up the Metadata to be displayed in the settings form as follows
Create a Layout at Administration -> Layout ->Forms -> +Add Form.
Select Content Mover-DMS from Where to be displayed.
Select the Source Template and Target Template, then click the Add to folder or Map to Folder button. Mapping
Add Metadata to be displayed on the Profile section and provide Access.
Click Save.
Metadata can be set as a default value or forced value.
Add Settings as follows:
Select whether or not to bring files like documents or shortcuts.
Note: Chat files are always saved as JSON file.
For subfolders, they are not allowed to be removed, all subfolders are synced to the target.
Mapping between a search folder is not permitted.
Mapping between a channel and Tab is not permitted.
Select whether or not to import the Post files into the teams/channels/tabs when moving.
Select to apply the system security either from Source or Target to the moved channel/team/tab.
The option to create new users would be visible if Source security is selected in the above step. It allows creating new users (if those do not exist) with three options as below:
Option | Description |
No Users | No new user is created; it applies default security Private to common user between Source and Target. |
Internal Users | Internal Users of Source system is created on Target system with default security Private. |
Every User | All users from Source system is created on Target system with default security Private. |
Click Save.
The mapping now is set up and displayed in the Default Settings tab.
Configuration
Go to the Configuration tab in Content Mover Manager.
Following screen displays -
The Cloud Provider and Storage are currently hardcoded to AWS and S3.
In the second Storage lookup, select the particular existing bucket. Or Set the Bucket Name to create a new Bucket.
Set the API Endpoint Base URL, the URL used for the CAM URL. E.g. https://firmname.prosperoware.io. Litera will share the URL.
Enter the API Secret Key configured from Azure Portal. Litera will generate and share the keys.
Click Validate and you should see a green bar on top of the page saying Validation Successful.
Note: Once validation is successful, the user adds a client token in the iManage server configuration. For more details iManage Server Configuration
Click Save. A validation message appears saying the Configuration was successful.
Action Status
This section describes the status of the sync configurations. You can view the sync status with error details and a retry option in case of sync configuration fails against your configuration from Team to iManage or vice versa.
Navigate to the Action Status tab, the following screen appears:
Fields | Description |
|---|---|
Action | Displays the list of action performed on workspace, folder, and document level |
Repository | Displays the list of repositories |
Database | Displays the list of databases |
From | Displays the list of Teams |
To | Displays the list of iManage workspaces |
Status | Displays the sync status either completed or failed |
Edited On | Displays sync date and time |
Error Message | Displays an error message in case of sync failure |
Error Details | Click Details to view error in details in case of sync failure |
Action | Click the Hamburger menu to perform a retry of the sync. Click Retry. Also, completed Content Mover Jobs can now be ad-hoc resynced from the Source system. The Resync button is visible in the Jobs user interface when the permission View Content Mover Resync is enabled.. Note: Only new or modified content will be resynced. Conversation files will also not be resynced. The Resync button will be disabled on the job after clicking Resync as it executes to prevent simultaneous jobs. Note: The retry option is only available if the sync fails. |
M365 to NetDocuments
Job
Allows the user to search, edit/update the config job. User can perform the following operations
Filter - Allows you to filter or search the config job based on the provided parameters.
Click the hamburger menu to upload the CSV:
Filter
Allows you to search the required config jobs. The following screen opens -
Fields | Description |
|---|---|
The filter option is divided into two parts as follow | |
Source option | Provide the source system details as follow -
NetDocuments doesn’t support the name of a tab to contain one of the following special characters: /:*?"<>| |
Target Option | Provide the target system details as follow -
NetDocuments doesn’t support the name of a tab to contain one of the following special characters: /:*?"<>| |
Click Search to display the result. The following screen appears -
Fields | Description |
|---|---|
Source | Display the list of the source system details (Office365) |
Target | Display the list of the target system details (NetDocuments) |
Details | Detail contains the following fields -
Note: View Content Mover Logs permission is required to see the Logs menu option. |
Click Clear to clear the fields
Editing Job Settings
Allows you to update the config job setting.
To Perform the edit job navigate to the Hamburger menu under Action
Fields | Description |
|---|---|
Enabled | Specifies the whether job is enabled. You can select the value. |
From System | Display the source system name. |
To System | Display the target system name. |
Repository | Display the repository name. You can change the repository from the dropdown list. |
Database | Display the database name. You can change the database from the dropdown list. |
Sync Option | Specifies the sync option. You can change the sync option as follows
|
Default Class | Display the current default class. You can select the default class from the dropdown list. |
Bring Post Files | Shows or hides the post files as per the option chosen by you on the Edit Job Settings screen. |
Apply Security | No action is required from you. By default, security of the Destination folder is applied on documents. Note: When documents are copied and synced across DMS systems, review the security of the Access Control List (ACL) as documents are accessible to anyone who has access to the destination folder.
|
Create new users (if doesn't exists) | Update the new user value by selecting an option. |
Settings | Enter the following values -
Note: If an existing OneNote is added inside a Team, and the Repository isn’t one that is subscribed to, the Job event won’t be triggered until a change is made, or the Repository is subscribed to. You can transfer your contents to NetDocuments by selecting one of the options:
Important: You can view in the NetDocuments, OneNote notebook is stored as a folder with a separate data file for each section. OneNote files have a .one filename extension.
You can transfer your contents to NetDocuments by selecting one of the options:
– This allows you to skip ahead in order to move contents. Skip is set by Default to skip for all Teams to NetDocuments jobs. Important: You can view in the NetDocuments, planner is stored as a folder with a separate data file for each section. Planner files have a .xlsx filename extension.
Note: When documents are copied and synced across DMS systems, review the security of the Access Control List (ACL) as documents are accessible to anyone who has access to the destination folder. When moving documents from Teams to a DMS the author of the document is now set to whoever modified the document last. Note: For NetDocuments, the user will be whoever last modified the document in Teams.
Users can assign a custom name to a team being copied from Warning: CAM will apply the Rule format "@system@_@clientId@-@matterId@" if the Rule format from Copy As is removed after saving. This is a CAM limitation. |
Update | Click Update to update the changes. |
Cancel | Click Cancel to close the dialog. |
Delete content mover setting
Allows the user to delete the content mover job. Following screen displays:
Enter reason to perform delete operation
Click Delete to remove the config job and click Cancel to close dialog
Default Settings
It displays all mapped content mover systems to run jobs off of. You can update the mapped content mover system settings.
Navigate to the Default Settings, appears the following screen:
Filter
Allows you to search the particular source and target system
You can add a new job mapping from source to target systems. After clicking Add New, displays the following screen:
Fields | Description |
|---|---|
Enabled | Specifies whether job mapping is enabled. Default value is Yes. |
From System | Specifies the content mapping source system. Select the source system from the drop down list. |
To System | Specifies the content mapping target system. Select the target system from the drop down list. |
New Interval | Specifies the content mapping interval. You can set an interval by selecting minutes, hour, and days. |
Profile | You can set content mover profile lookup in layout. For more information on layout click here. After configuring profile layout lookup, select from dropdown list. |
How would you like to sync documents? | Specifies how to sync the documents. Select an option. |
Bring Post Files | Select an option. |
Apply Security | No action is required from you. By default, security of the Destination folder is applied on documents. Note: When documents are copied and synced across DMS systems, review the security of the Access Control List (ACL) as documents are accessible to anyone who has access to the destination folder.
|
How to handle Team | Specifies how to handle Team by selecting an option. |
How to handle Channels | Specifies how to handle Channel by selecting an option. |
Click Save to add new mapping job or click Cancel to close dialog
In Search results navigate to Action, you can perform the following actions -
Update the existing job setting
Delete the job setting
Configuration
After adding the new mapping now you can configure Client API configuration
Navigate to the Configuration tab, the following screen appears:
Fields | Description |
|---|---|
Choose Cloud Provider | Specifies the configured cloud provider. Select the value from the dropdown list AWS or Azure based on your setup. |
Choose Storage | Specifies the configured storage. Based on the cloud provider the option displays in the dropdown list. |
Choose Storage Type | Specifies the storage type. You can select either Prosperoware Encrypted Storage or the Private Encrypted Storage on your Private Cloud. Prosperoware Encrypted Storage(AES-256) Private Encrypted Storage(Private Cloud) |
Bucket Name | Specifies the configured Bucket name in Azure. For more information click here. Enter the Bucket name. |
API Endpoint Base Url | Specifies the configured Bucket name in Azure. For more information click here. Enter the API Endpoint Base Url. |
API Secret Key | Specifies the unique secret key configured in Azure. Enter the API secret key. |
Validate | Click “Validate” to validate the form data. If the form data is correct, then the message “Validated successfully” will be displayed. |
Click Save. A validation message appears saying the Configuration was successful
Click Cancel to cancel the Client API setting configuration
Action Status
Displays status of the all jobs in Completed, Failed. Navigate to the Action Status tab, appears the following screen:
Fields | Description |
|---|---|
Action | Displays the action icon. Specifies the performed action. |
Repository | Displays the list of the repositories. |
Database | Displays the list of the database. |
From | Displays the list of the source systems. |
To | Displays the list of the target systems. |
Status | Displays the list of the status, Completed, Failed. |
Error Message | Displays the error message for the failed jobs. |
Error Details | Click on the Details opens the dialog with error details. |
Action | Click the Hamburger menu to perform a retry of the sync. Click Retry. Also, completed Content Mover Jobs can now be ad-hoc resynced from the Source system. The Resync button is visible in the Jobs user interface when the permission View Content Mover Resync is enabled.. Note: Only new or modified content will be resynced. Conversation files will also not be resynced. The Resync button will be disabled on the job after clicking Resync as it executes to prevent simultaneous jobs. Note: The retry option is only available if the sync fails. |
Shortcuts will be tracked for audits during a full sync but not on delta syncs (daily syncs).
Exporting from Content Mover
Information can be exported from Content Mover like chat files. To do this, you will need to call the API with this configuration. For more information reach to Litera Customer Care for API information they can share directly to you, or Professional Services.
{{host}}/api/v1/Content Mover-manager/content-sync/Content Mover/actions/create-html/request
Request Body
{
"objectMappingId": 73962,
"objectType": "folder",
"action": "CREATE_HTML",
"saveAs":"chat_file_save_as_test"
}
The object mapping id is needed to map to the chat or object.
Object type is the type of object (chat, folder, document)
Action to save is Create_HTML
Saveas is if you want to specify a name for the file when it is saved.
The file will be then saved in the team’s conversation.
Note: PDF file saving is not currently supported.