Migrate from Pegasus Systems to Asana

Pegasus Client records (contact information, campaign history, performance analytics) map to Asana Projects. The primary contact on the Pegasus client becomes a Project Member in Asana. Client-level custom properties from Pegasus migrate as custom fields on the Asana Project. We use the Asana API to create each project with the correct name, notes (pasting the client description), start date (from Pegasus job start), and team assignment.

Pegasus Jobs are the project-level container holding timelines, task lists, and resource allocation data. Each Pegasus Job maps to one or more Asana Tasks (or a Task with subtasks representing sub-deliverables). Job status, dates, and custom fields migrate as task fields and custom fields in Asana. Job-to-Client association becomes Task-to-Project membership. The Job timeline becomes the task Due Date in Asana with start date stored as a custom field since native start dates are only available in Timeline view on Advanced and above.

Pegasus per-minute timesheet entries (billable and non-billable flags, user assignment, date, project association) map to Asana tasks with time recorded in custom numeric fields. Each distinct timesheet entry becomes a task record; billable flag maps to a single-select custom field (Billable / Non-billable), and the minutes value maps to a numeric custom field. For agencies requiring aggregated time reporting, we recommend enabling the Asana Time Tracking add-on or a third-party integration (Harvest, Toggl) post-migration. Pegasus Excel timesheet exports are parsed and chunked into individual task records for bulk import.

Pegasus Expense records (vendor, amount, date, job association) map to Asana tasks with custom fields capturing vendor name, amount, and expense category. The Expense-to-Job lookup becomes a Task-to-Project association. We flag during scoping whether the destination org uses the Asana Expenses by Harvest integration or requires standalone task-based tracking. Accounts Payable approval workflows from Pegasus do not migrate; we document them as Asana Rules to rebuild.

Pegasus Invoice records (headers, line items, amounts, payment status) have no direct Asana equivalent because Asana does not include an invoice or financial module. We extract invoice metadata and flag it as a candidate for an Asana Custom Object (available from Asana Business tier) or for reconstruction as a linked PDF document attached to the relevant Project. Closed or locked financial periods in Pegasus require manual reconciliation with the customer's accountant before migration; we document locked-period invoices separately.

Pegasus Media Campaigns aggregate real-time metrics, client meetings, and new projects into a single view. We extract campaign metadata and current metric values as a static snapshot stored in Asana Project custom fields. Live connector data does not transfer. We recommend documenting live campaign metrics state in the project description or a pinned task at project top for reference.

Pegasus holds assets, cash flow statements, and chart-of-accounts data in its finance layer. This data has no Asana equivalent and is outside the scope of a project management migration. We flag the existence of these records, recommend exporting the chart-of-accounts and current balances as a CSV for the customer's finance team to load into their accounting tool (QuickBooks, Xero, or similar), and note that any historical transaction detail that needs preservation requires a separate accounting-data migration engagement.

Pegasus user accounts map to Asana Users. We extract user records with role information and map them to Asana Workspace members. Active vs inactive status is preserved. During migration, the Asana Workspace must be provisioned before any task import so that Owner references on Pegasus Jobs resolve to valid Asana User IDs.

Pegasus custom fields on Jobs and Clients require explicit field-level mapping to Asana custom fields. We document all Pegasus custom field names and data types during discovery, then pre-create the equivalent custom fields in Asana (single-select, multi-select, text, numeric, date) before migration. Each custom field pair is added to the migration scope and mapping document. This is a manual preparation step in Asana admin that cannot be automated before the migration run begins.

Documents and files attached to Pegasus Jobs, Clients, or Invoices are extracted as binary blobs or URLs. We preserve attachment associations by linking them to the migrated record in Asana via the Asana Attachments API. Attachments exceeding 100MB cannot be processed by the Asana API; these are flagged and stored with a URL reference to the source file for manual retrieval. We document all large-file attachments during discovery for customer resolution.

Pegasus workflow automations and approval processes do not have a direct Asana equivalent and are not migrated. We deliver a written inventory of every active Pegasus workflow, its trigger conditions, actions, and approval chain, with recommended Asana Rules equivalents documented for the customer's admin to rebuild. Workflow rebuild sits outside the data migration scope.

Pegasus custom reports do not migrate. We document every Pegasus report configuration (report name, filters, groupings, output format) during discovery and flag which reports the customer considers critical. The customer recreates these reports in Asana Dashboards or exports them to a BI tool. Reports referencing locked financial periods in Pegasus require additional reconciliation before the data they reference is available in Asana.