Migrate from OnePlan to Microsoft Project

OnePlan Plans map directly to Microsoft Project MPP files. We export each Plan as a separate CSV from the Migration Tool, then convert to MSP task structure. If the source OnePlan environment uses multiple Areas, we create one MPP file per Plan or group Plans by Area into separate files. The Plan name becomes the MSP project name, and the Plan type hierarchy is flattened to summary tasks in the MPP file.

OnePlan Work Plans map to MSP task lists. The Work Plan name becomes the MSP project summary task or a top-level summary task. Tasks within the Work Plan become child tasks under the summary. We preserve the outline level by mapping OnePlan's Work Plan hierarchy to MSP's WBS outline structure. Estimated Start and Estimated End dates from OnePlan migrate as Start and Finish fields in MSP.

OnePlan Tasks map directly to MSP tasks. Task name, Start, Finish, Duration, Percent Complete, and Priority transfer directly. Dependencies defined in OnePlan (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) map to MSP predecessor links. Note that imported tasks in OnePlan do not auto-reschedule until opened in OnePlan's UI; we pull the manually corrected schedule dates rather than relying on OnePlan's calculated Estimated Start/End.

OnePlan Resources map to MSP Resources. We export resource data from the Migration Tool and create MSP resources with Name, Type (Work or Material), Max Units, Cost Rate Table entries, and any resource-level custom fields. Material resources in OnePlan map to Material type resources in MSP. Resource allocations from time-phased resource plan data map to MSP Assignment rows (Start, Finish, Units) on the related tasks.

OnePlan Risks are sub-entities under Work Plans. We map Risk Title, Probability, Impact, Status, and Owner to custom task-level text or flag fields in MSP (Risk_Title, Risk_Probability, Risk_Impact, Risk_Status). If the risk count per project is low, we store them as a separate Risk Register worksheet within the same workbook rather than custom fields. Full risk register functionality requires a separate risk database tool.

OnePlan Issues map similarly to Risks. Issue Title, Priority, Status, Owner, and Description transfer to MSP custom fields (Issue_Title, Issue_Priority, Issue_Status) or a separate Issues section in the project notes. Issues requiring workflow tracking (assignment, escalation, resolution) do not have an MSP equivalent and must be handled in a separate ticketing system post-migration.

OnePlan's Financial Plan module (CapEx, OpEx, forecasts, actuals by period) does not have a direct MSP equivalent. We split this data: cost amounts by period map to MSP Cost Resources on the relevant tasks (with time-phased cost entries as Assignment Budgeted Cost fields if the customer's MSP version supports them). Summary financial data (total budget, spend to date, forecast) becomes a Project Summary custom field or a separate Finance worksheet in the workbook. Full financial plan continuity requires a separate financial tracking system.

Resource allocation over time from OnePlan's Resource Plans maps to MSP Assignment rows in the Resource Usage view. We preserve allocation percentages and dates across periods as Assignment Max Units values for each time-phased row. Peak allocation and capacity planning data from OnePlan transfers as resource Max Units and peak utilization flags.

OnePlan's seven custom field types map to MSP equivalents: Text maps to Text custom fields; Date maps to Finish custom fields (or custom start/finish variants); Number maps to Number custom fields; Currency maps to Cost custom fields; Yes/No maps to Flag custom fields; Choice maps to Outline Code or Text custom fields with a lookup table; User maps to Text custom fields (MSP has no native User reference type). We preserve the original OnePlan field name in the MSP custom field name for auditability.

OnePlan's hierarchical Plan types (Program containing Project) have no direct MSP equivalent — MSP files are flat project containers without a native program entity. We handle this by creating one MPP file per Plan, then grouping them into a shared SharePoint library or Project Server/PWA workspace where the program relationship is managed at the SharePoint folder level rather than inside the file. Alternatively, we create a master MPP with summary tasks representing the program and subproject links (Insert > Subproject) if the customer uses PWA.

OnePlan milestone tasks marked as such migrate to MSP tasks with Duration = 0 and Marked as Milestone = Yes. Milestone name and date transfer directly. Milestone dependencies (predecessors driving the milestone) also transfer as MSP predecessor links.

OnePlan document links and attachments stored in SharePoint do not migrate through the CSV Migration Tool. We flag every SharePoint document URL associated with a Plan or Work Plan and deliver a written inventory listing the source URL, the target SharePoint location, and the recommended re-link action in Microsoft Project (Insert > Hyperlink or SharePoint Document Sync). This is a manual post-migration step.