Best Practices

Adding not Updating

This Tool was designed for one-time migrations and not intended for ongoing production use. It can only add data to OnePlan, it will not update or remove any existing data.

Release Day

Please do not plan to run a migration on a OnePlan or OneConnect release day. Please review the release calendar in advance of your planning.

Schedule

When adding tasks to a plan using the Migration Tool, they will not be automatically rescheduled until a user opens that plan using OnePlan.  

The Estimated Start and Estimated End dates in OnePlan are special fields. These dates will change as tasks are added or updated within the schedule in the Work Plan. 

However, in order to properly import tasks, make sure you set the estimated start date for the parent plan and import that first. After that, import the schedule for that plan, before you open the plan in OnePlan.

The scheduling engine in OnePlan factors in many settings when working on the calculations. If you get start and due dates that do not match you expectation it is recommended to check these fields on the task(s):

Start Date

Duration

Predecessors/successors (if you use that, the type and the lag time)

Calendar

Scheduling Mode

Manually Scheduled flag

Constrain Type (and date if applicable)

The work start and end time in the calendar will also impact the scheduling engine's logic.

Rerunning Migrations

As the tool does not update data, please follow theses steps when re-running the migration:

• Review which plans need to be updated and only includes those in your files.
• Bulk delete any plans that you include in your source files.
• Re-run the import tool.

Import Order

To ensure dependencies are respected, import data in the following order:

1. Resources
2. Plans
3. Work Plans
4. Resource Plans
5. Financial Plans

Tips

• The tool does not support stopping mid-process. Once you start the migration for an entity, that will import all the data. Always test with small datasets first.
• Some source systems like Project Online supports a % based lag time. You can only set days as lag time in OnePlan, so you must convert the % to days before you import your data.
• Rows or fields beginning with # in the CSV files are treated as comments and ignored.
• Do not name any column “ID” or “MapId” in your CSV files, those names are considered “Reserved” and unexpected behavior may occur if these values are mapped.
• System fields that are calculated in OnePlan should never be mapped. These have a type of "Calculated", "Roll Up", or "Trend". Example:
  • Actual Hours
  • Actuals
  • Benefits
  • Budget
  • Committed Effort
  • Count
  • Estimated End
  • Forecast
  • Governance Problems
  • Governance Warnings
  • Plan Count
  • Program Budget
  • Timesheet Charge
  • Timesheet Type

Support

• For guidance, reach out to your OnePlan contact.