Migrate from Monograph to Microsoft Project

Monograph Projects map to Microsoft Project plans with the project-level metadata (name, start date, deadline, status, client association) preserved in project summary fields. The phase and sub-project hierarchy migrates as a WBS task structure with summary tasks representing phases and tasks representing line items. We extract the phase-level budget values from Monograph's budget records and enter them as custom number fields or cost fields on the corresponding summary tasks in Microsoft Project.

Monograph phases and cost codes map to a combination of Microsoft Project summary tasks (for phase grouping) and custom text or number fields for cost-code identifiers. We extract the phase structure during scoping and build the WBS numbering scheme that maps cleanly into Microsoft Project's outline numbering. Cost codes that exist in Monograph but not in the destination Project plan are flagged as fields requiring setup before migration.

Monograph timesheet entries map to Microsoft Project task assignments with actual work hours recorded. We extract billable hours, non-billable flags, date, staff member, and project-phase association. In Project desktop and Project for the web, actual work on assignments represents the hours recorded. The destination resource (mapped from Monograph staff) must exist before assignment import. Note: Microsoft Project does not have a native timesheet approval or submission workflow; this process is manual or requires Project Server Subscription Edition with PWA timesheet module.

Monograph staff records map to Microsoft Project Resources. We extract name, role (Principal, Project Manager, Staff), and hourly rate. Role-based Monograph access (Principals, PMs, Staff) does not migrate as permissions; we map roles to Resource custom fields or Resource Groups in Microsoft Project. Active projects in Microsoft Project require the Resource pool to be populated before assignment import so that OwnerId lookups resolve correctly.

Microsoft Project has no native Client object. We map Monograph Clients to a combination of a custom text or lookup field on the project plan and optionally a SharePoint Contact list in the associated Project Online site. Client contact information (name, company, email) migrates as a custom field value on the project record. Client portal access settings from Monograph cannot be reproduced in Microsoft Project; we document them as a manual reconstruction item for the customer's admin.

Monograph Invoices have no direct Microsoft Project equivalent. Invoice records (headers, line items, payment status, write-off decisions) do not migrate as working records. We extract the invoice history during scoping, preserve it as a written record and CSV export, and document the monetary totals per project so that the customer can reconstruct billing records in their accounting software or a companion billing tool post-migration. Write-off decisions are explicitly called out in the financial summary because they affect unbilled totals.

Monograph project budgets tied to phases or cost codes migrate as Microsoft Project custom number fields on the corresponding summary tasks. Over-budget flags and amendment history are preserved as notes on the project record. We extract budget-versus-actual data during scoping and map it to Microsoft Project's Earned Value Management fields if the customer requires earned value tracking on Plan 3 or Plan 5.

Monograph custom fields on Projects migrate to Microsoft Project custom fields of the matching type (text, number, date, choice). Microsoft Project supports up to ten custom fields per project plan and allows up to 30 custom fields on Project Online enterprise project types. We pre-create the custom field schema in the destination before migration and map values during the import phase. Fields without a direct type equivalent are flagged during scoping.

Monograph Workflows automate repetitive project tasks but have no direct Microsoft Project equivalent. Microsoft Project does not include a native workflow engine; automation at the enterprise level uses Power Automate with Project Online connectors or Project Server event handlers. We extract the Monograph workflow definitions and trigger conditions during scoping and deliver a written workflow inventory with Power Automate equivalents. The customer's admin or a Microsoft partner rebuilds these post-migration.

Monograph PTO balances do not migrate as live balance records. We extract the balance snapshot at migration time and document it as a note on the staff member's resource record. Microsoft Project and Project Online do not have a native PTO tracking module. If the firm requires ongoing PTO tracking, this is managed outside the PM tool or through a dedicated HR system.