Before you migrate your data into OnePlan, some configuration activities must take place in OneConnect.

Field Mapping

Fields must be mapped between your source files and OnePlan. This is required as you can use any field name in your source files.

Once you load the Migration Tool, click on Mappings:

Each entity has a section. Open each section and map the field based on the recommendations below.

Note that the left side of the mapping is the source field names. Your field names may be different.

Plans

Beyond the minimum fields you can also map custom fields as required.

The following fields must be mapped for plans:

The text field called "Project Code" was used in the example above. You can name your Plan External ID anything you want.

Beyond the minimum fields you can also map custom fields as required.

The following fields must be mapped for work plans:

The minimum field mapping will only create a very basic item in the work plan.

The recommended mapping includes many built in fields to provide a more realistic scenario:

Beyond the minimum fields you can also map custom fields as required.

The following fields must be mapped for resource plan migration:

Beyond the minimum fields you can also map custom fields as required.

The following fields must be mapped for financial data migration:

Related to