Project Migrator supports mapping Project Online project fields to related tables in Planner Premium. This functionality is available through the Related Field Mapping section and allows you to populate related tables in Planner Premium during migration by configuring the field mappings between Project Online Project fields and the selected related table fields.
The Related Field Mapping feature is designed to support any related table configured in Planner Premium.
Typical use cases include migrating:
- Project Lifecycle information
- Status Reports
- Risks
- Issues
- Other custom related entities
Although the fields differ between tables, the configuration process remains the same.
If no additional data needs to be migrated, you can simply leave this section empty. Existing migrations continue to work exactly as before.
Configuring Related Field Mapping
When migrating data from Project Online to Planner Premium, after selecting the source (Project Online) and target (Planner Premium) systems, the Related Field Mapping section appears beneath the standard Project Field Mapping.
If no additional data needs to be migrated, you can simply leave this section empty.
To configure a related table, perform the following:
- Navigate to the Related Table Mapping section and click Add Related Table.
- Select the target related table (for example, Project Lifecycle).
- Choose the Record Creation Mode for the selected table:
- Create or update the latest record (this option allows you to create new records or merge data into existing ones).
- Delete existing records and create a new record (this option allows creating new records from scratch and deleting existing records).
- Always create a new record (this option allows you to create a new record on the target, regardless of whether previous records already exist).
- Use the Add Mapping button to configure the field mappings between Project Online Project fields and the selected related table fields. Add as many mapping fields as needed.
- Map the lookup values if needed.
If the source and target stage names are identical, no additional lookup value mapping is required. Project Migrator automatically matches the corresponding stage.
If the values differ, you can configure custom lookup mappings to move source values into the appropriate Planner Premium values.
- Save the mapping by exporting it to Excel for reuse in future migrations.
In the same way, add as many related tables and field mappings as needed.
Example: Project Lifecycle Mapping
Each related table has its own independent field mapping configuration.
In this article, we review the detailed mapping process, using the Project Lifecycle as an example. The same mapping principles apply to other related entities.
As an example, we will take a common requirement: migrating the current project lifecycle from the closed workflow stage in Project Online to the Project Lifecycle table in Planner Premium, in the closed (finished) status.
The fields from both systems (source and target) will need to be mapped carefully, including the lookup values, if they differ.
However, simply mapping the project to the final stage may not complete the workflow, as Planner Premium also requires additional status fields to indicate that the workflow has finished.
To automate this process, we will need to configure additional mappings for the source Lifecycle Active Stage field to the target workflow status fields, such as:
- Active Stage (Closed)
- Status Reason (Finished)
- Status (Inactive)
Using conditional mappings, Project Migrator can automatically assign the correct values if the source project is in a completed stage.
With these mappings in place, migrated projects appear as fully completed workflows, requiring no manual updates after migration.
