Migrate from Pegasus Systems to Microsoft Project

Pegasus Clients with contact information, campaign history, and performance analytics have no native equivalent in Microsoft Project. We map the primary client name and contact to a project-level custom field (Client Name, Client Contact) and store the full client record in a companion SharePoint List linked to the project site. If the destination is Project Online, the client metadata lives in a PWA enterprise custom field lookup table.

Pegasus Jobs are the project-level container holding timelines, task lists, and resource allocation data. Each Job maps to a Microsoft Project file (MPP or PWA project). Pegasus job status, start date, finish date, and custom properties migrate to Project-level custom fields. We extract task lists from Pegasus and reconstruct them as a WBS hierarchy in Microsoft Project, with Pegasus task order preserved as WBS outline position.

Pegasus Jobs contain hierarchical task structures that map to Microsoft Project Tasks with a WBS outline. We parse the task hierarchy from the Pegasus export, set Task Name, Start, Finish, Duration, and Predecessors (where dependencies are expressed), and preserve the original Pegasus task order as WBS number. Task-level custom fields from Pegasus map to local Microsoft Project custom fields or enterprise custom fields depending on whether the destination is PWA.

Pegasus Users and Owners with role information map to Microsoft Project Resources. We extract all distinct Pegasus users referenced on Jobs, Timesheets, and Expenses, create a Resource record for each, and set the Resource Type (Material or Work). Max Units are set to 100% for named resources unless Pegasus timesheet utilisation data indicates otherwise. Resource rates are populated from Pegasus user role data where available.

Pegasus Job resource allocation data maps to Microsoft Project Assignments. Each assignment links a Resource to a Task and carries Assignment Owner, percent allocation, and start/end dates. We compute Work (in hours) from Pegasus allocation percentages and project duration, and set Assignment Units to the Pegasus allocation fraction. Overtime work flags from Pegasus map to Assignment overtime fields where supported.

Pegasus Timesheets with per-minute billable and non-billable flags have a structural mismatch in Microsoft Project. Project stores actual work against Assignments, not as a standalone timesheet object. We aggregate Pegasus timesheet entries by task and user, set Actual Work on Assignments, and mark the task Status Percent Complete from the aggregated timesheet data. Billable/non-billable flags are stored in custom fields. Note: Microsoft Project does not natively replace a timesheet approval workflow; Project Online requires a separate timesheet solution (Project Time or a third-party add-in).

Pegasus Expense records with vendor, amount, date, and job association have no native home in standard Microsoft Project. We map expense amounts to task-level Cost fields where a 1:1 expense-to-task relationship exists, and to project-level custom fields (Total Expenses, Budget Variance) for summary expense data. Full expense ledger with vendor detail is exported separately as a CSV for the customer to import into an accounting tool or Power BI.

Pegasus Invoices generated from job costs and timesheet data cannot migrate into Microsoft Project. Project has no invoice object. We extract invoice headers, line items, amounts, and payment status as a structured CSV export. The customer reconciles this with their new accounting or invoicing tool post-migration. Locked financial periods in Pegasus are flagged during scoping; we do not attempt to reopen or re-post to locked periods.

Pegasus Media Campaigns aggregate campaign metadata, client meetings, and new projects. We extract campaign name, status, start/end dates, and key metadata as project-level custom fields in Microsoft Project. Live metrics from Pegasus are migrated as a static snapshot; real-time campaign analytics require a connector to the media platform (Google Ads, Meta Ads, etc.) that is outside Microsoft Project's native scope.

Pegasus custom fields on Jobs require explicit per-field mapping to Microsoft Project custom fields. We document all Pegasus custom field names, data types, and picklist values during discovery. Text fields map to Microsoft Project custom text fields; numeric fields map to cost or number fields; picklist values map to custom flag or text fields. For PWA destinations, we provision enterprise custom fields before migration. For MPP desktop destinations, we add local custom fields per project file.

Documents and files attached to Pegasus Jobs, Clients, or Invoices are extracted as binary blobs or URLs. We preserve attachment associations by mapping each attachment to the corresponding document library in the destination SharePoint site (for Project Online) or a named folder alongside the MPP file (for desktop). Large binary blobs (>50MB) are skipped and listed in a gap report for manual handling.