Syncing Content from M365 to DMS
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 configurations, 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.
- 1 License and Add-on Requirements
- 2 Accessing Content Mover Manager
- 3 M365 to iManage
- 3.1 Office365 Jobs
- 3.2 Edit the Content Mover Job
- 3.2.1 OneNote
- 3.2.2 Planner
- 3.2.3 Copy to Site (Sharepoint)
- 3.2.4 Template Mapping
- 3.3 Delete the content mover setting
- 3.4 Default Setting
- 3.5 Adding a New Mapping
- 3.6 Configuration
- 3.7 Action Status
- 4 M365 to NetDocuments
- 4.1 Job
- 4.2 Editing Job Settings
- 4.3 Default Settings
- 4.4 Configuration
- 4.5 Action Status
- 5 Exporting from Content Mover
- 6 Related Topics
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!
M365 to iManage
M365 to NetDocuments
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.
Related Topics
Let's Connect📌
☎ +1 630.598.1100
☎ +44 20 3880 1550
📧 support@litera.com
💻 https://www.litera.com/support/
📝 Support is available:
4 am - 8 pm US Eastern
(9 am - 1 am GMT/BST
7 pm - 11 am AET) on normal business days (excluding holidays)
© 2024 Litera