Mapping Tool
The Mapping Tool is the screen in Xill4 where you build the mapping of a migration. In it, you decide where the source data goes on the target:
- Structures: which source folder goes to which target folder
- Content types: which source content type becomes which target content type
- Metadata fields: which source property fills which target field, and how
- Principals: which source user or group becomes which target user or group
- Permissions: which source permission becomes which target permission level
You work through these five steps one by one. Each step shows what is still unmapped and flags rows that need a fix. When you're done, you export the mapping as a Mapping Sheet that the transformation flows read.
When to use it
The Mapping Tool is the preferred way to build the mapping when you migrate from one of the source systems below to one of the target systems below.
Source systems
- Alfresco
- Documentum
- eDOCS DB
- File System
- FileNet Hybrid
- HP TRIM
- NetDocuments
- OnBase
- OpenText Content Server
- OpenText Content Server DB
- SharePoint On-Premise
Target systems
- Alfresco
- Documentum
- NetDocuments
- OpenText Content Server
- SharePoint Online
For any other source or target system, fill in the Mapping Sheet in Excel, as described in the Mapping Sheet Overview.
How it fits in a migration
| Step | What you do | Where |
|---|---|---|
| 1 | Extract the source and the target to MongoDB with their connectors. | Extraction flows |
| 2 | Create a mapping: read the extracted data from MongoDB, or import a Mapping Sheet. | Mapping Tool |
| 3 | Map each step: Structures, Content Types, Metadata, Principals and Permissions. | Mapping Tool |
| 4 | Review and export the mapping as a Mapping Sheet. | Mapping Tool |
| 5 | Put the exported file where the transformation reads its Mapping Sheet, and run the transformation. | Transformation flows |
When the source or the target changes, for example after a new extraction, reload the data. Your choices are kept.
The Mapping Tool takes over the parts of the Excel workflow that you would otherwise do by hand:
- Prefilling. Reading the data from MongoDB replaces the Populate Mapping Sheet flow.
- Mapping. You pick targets from lists that only offer values that fit, instead of from the dropdowns of the workbook.
- Checking. The checks run while you map, instead of as colored cells.
Open the Mapping Tool
- Open a project.
- In the project toolbar, click Mapping.
The Mapping Tool opens on its start screen. To return to the project, click Back to project in the toolbar.
Where mappings are stored
A mapping is stored in MongoDB, in the mappingSets collection of the source database you choose on the start screen. Everyone who opens the Mapping Tool with the same environment and source database sees the same mappings, and can continue where someone else left off.
Deleting a mapping removes it and all its choices from that collection. The extracted source and target data, and any Mapping Sheet you imported, aren't touched.
Saving your work
Not every change is saved the same way:
| Change | Saved |
|---|---|
| Picking a target, setting No op, changing a setting, adding or removing an extra column | When you click Save |
| Adding a row, adding a target value, deleting a row, moving a row | Right away |
The bar at the top of a mapping shows Unsaved changes or All changes saved. If you leave with unsaved changes, for example with All mappings or Back to project, the Mapping Tool asks you to confirm first. Exporting saves your changes before it creates the file.