Migrate from iPlan to Microsoft Project

iPlan Projects map directly to Microsoft Project plan files or Project Online projects. We extract project-level metadata including project name, status, planned start and finish dates, budget amounts, project owner, and description. The project-level hierarchy in iPlan (parent portfolios and child projects) maps to Microsoft Project Plan 3 Roadmap aggregation or a flat project list with cross-project dependency links. Projects with no tasks are imported as empty plans with metadata preserved.

iPlan Tasks map to Microsoft Project Tasks with standard fields including Task Name, Start, Finish, Duration, and Predecessors. Task description maps to the Notes field. Priority and status values map to custom fields or text fields depending on the destination Project tier. Task-level custom fields (dropdown, numeric, text) map to Microsoft Project custom fields with explicit type matching to avoid import errors.

iPlan Milestones map to Microsoft Project Milestones. We set the Milestone flag and preserve the target date. Milestones without linked tasks are flagged during validation because they represent orphaned schedule markers in the destination. Cross-project milestone dependencies are documented separately as a dependency map for manual reconstruction in the destination Roadmap or project plan.

iPlan Subtasks are child tasks within a task hierarchy. Microsoft Project supports nested task outlines natively. We import nested subtasks as child rows under their parent Task. If the destination Project Online instance has outline level restrictions, we flatten subtasks into a flat task list with a custom ParentTaskId field preserving the hierarchy reference.

iPlan Resources (employees with roles and availability schedules) map to Microsoft Project Resources. We extract resource name, initials, type (work or material), max units, and hourly rate. iPlan's availability calendar data transforms to Microsoft Project resource calendar entries. Generic resources map to Resource type Generic; named employee resources map as standard Resources with resolved calendar exceptions for PTO and capacity changes.

iPlan task assignments (resource linked to task with hours or percentage allocation) map to Microsoft Project Assignments. We resolve the assignment by matching the iPlan resource reference to the migrated Microsoft Project resource record, then create the assignment with Work (hours) and Units (percentage) values. Over-allocation detection is enabled in the destination but requires resource calendar accuracy during import.

iPlan Timesheet entries (hours logged, date, project association) map to actual work values on Microsoft Project Assignments or as Task Update records in Project Online. We preserve hours, date, and task linkage. Timesheet entries with orphaned project references (projects deleted in iPlan but with logged hours) are flagged in the reconciliation report. Financial billing data derived from timesheets does not have a direct Microsoft Project equivalent and is noted separately for billing module reconstruction.

iPlan's earned-value metrics (Planned Value, Earned Value, Actual Cost, and derived indices) do not have native Microsoft Project fields. We extract the metric values as custom number fields (ev_planned_value__c, ev_earned_value__c, ev_actual_cost__c) and preserve the last-calculated date. Formulas that iPlan computes automatically must be rebuilt as custom calculated fields in Microsoft Project if the destination supports them, or tracked manually post-migration.

iPlan custom fields on Projects and Tasks require explicit type mapping before import. Dropdown fields map to Project custom picklist fields; numeric fields map to number fields; text fields map to text fields. Formula and rollup fields do not have portable equivalents and are recreated as Microsoft Project calculated fields or noted for manual post-migration setup. We document every custom field with its source type, destination type, and any transformation logic.

iPlan knowledge-base articles export as structured text content. We preserve article titles, body content, and attachment file names. Article category taxonomy does not map cleanly to Microsoft Project's flat document model, so we map categories to SharePoint folder structures or assign as label custom fields on the migrated documents. Attachments export as files and upload to the destination SharePoint library or OneDrive location with original file names and upload timestamps preserved.

iPlan workflow automation rules encode business logic in a proprietary format that cannot be directly transferred. We extract every active workflow rule as a human-readable specification: trigger conditions, criteria, and actions. This specification is delivered as a written inventory document. The customer's admin rebuilds equivalent logic in Microsoft Power Automate or within Project Plan 3's built-in automation if available. We do not migrate workflow rules as executable code.

iPlan report configurations and dashboard visualizations use proprietary schemas that cannot be directly migrated. We export the underlying data (projects, tasks, resources, timesheets, earned-value figures) into a staging format that Power BI can consume. We deliver a report rebuild guide specifying which source objects and fields map to recommended Power BI visualizations. The customer's admin or a Power BI partner rebuilds the actual reports post-migration.