Migrate your Pegasus Systems data

Client records in Pegasus store contact information, campaign history, and performance analytics. We map the primary contact fields and client-level custom properties to the destination's equivalent Account or Contact object, preserving campaign association links as tagged records.

Jobs are the project-level container in Pegasus and hold timelines, task lists, and resource allocation data. We extract all job fields including status, dates, and custom fields, then map them to the destination's Project or Deal object. Custom fields on Jobs require field-level mapping during scoping.

Pegasus tracks time by the minute across multiple projects with billable and non-billable flags. We extract timesheet entries with project association, user assignment, and date. The destination's time entry schema must be confirmed to correctly map billable/non-billable designations.

Expense records in Pegasus capture AP data tied to jobs or clients. We extract expense entries with vendor, amount, date, and job association. Mapping to the destination requires confirming whether the target uses a flat expense list or job-linked expense records.

Invoices are generated from job costs and timesheet data. We extract invoice headers, line items, amounts, and payment status. Closed or locked financial periods in Pegasus require manual reconciliation flags in the destination to avoid period conflicts.

Media Campaigns in Pegasus aggregate real-time metrics, client meetings, and new projects into a single view. We extract campaign metadata and snapshot the current metrics state. Live data connectors cannot be migrated as live; they land as static records at migration time.

Pegasus holds assets, cash flow statements, and chart-of-accounts data at the finance layer. We extract the accounts structure and current balances but note that historical transaction history may require period-by-period re-entry depending on destination accounting module capability.

Pegasus supports custom fields on Jobs, Clients, and other objects. We document all custom field names and data types during discovery. Each custom field requires explicit field-level mapping to the destination schema, as Pegasus custom field naming conventions may not match target field names.

Documents and files attached to Jobs, Clients, or Invoices are extracted as binary blobs or URLs. We preserve attachment associations by linking them to the migrated record in the destination. Large binary attachments may require chunked transfer for stability.

Pegasus user accounts map to Owners or Assignees in destination systems. We extract user records with role information and map them to the destination's user management schema. Active vs inactive status must be preserved to avoid licensing surprises in the destination.