Migrate from Pegasus Systems to monday Work Management

Pegasus Client records store contact information, campaign history, and performance analytics. We extract primary contact fields and client-level custom properties, then map them to a monday.com Board where each client gets a dedicated board, or to a Clients board with Items representing individual clients. The mapping type depends on whether the customer's workflow is client-centric (board per client) or project-centric (single board with client as a connected board or Team column). We preserve any historical campaign performance data as static column values.

Pegasus Jobs are the project-level container holding timelines, task lists, and resource allocation data. We extract all job fields including status, start and end dates, custom fields, and resource assignments. In monday.com this maps to either a dedicated Board per Job or Items grouped within a Board by client. Custom fields on Pegasus Jobs map to typed monday.com columns. The customer's workflow determines whether Jobs become boards or items; we confirm the structure during discovery.

Pegasus timesheet entries track time by the minute across multiple projects with billable and non-billable flags. We extract entries with project association, user assignment, date, duration, and billable flag. In monday.com we map each timesheet entry to an Item with a Time Tracking column capturing duration, or to a separate Worklog board linked via Connect Boards column. The billable flag maps to a Status or Label column. Where Pegasus stores aggregated weekly timesheets, we split them into daily entries to preserve granularity.

Pegasus Expense records capture AP data tied to Jobs or Clients with vendor, amount, date, and job association. We extract all expense fields and map them to Items in a dedicated Expenses Board with columns for Vendor, Amount, Date, Status, and Job (via Connect Boards or Team column). monday.com has no native AP module, so expense status workflow (Pending, Approved, Paid) requires configuration in the automation builder post-migration.

Pegasus Invoices are generated from job costs and timesheet data with headers, line items, amounts, and payment status. We extract invoice records and map them to Items in an Invoices Board with columns for Invoice Number, Client, Amount, Status (Draft, Sent, Paid, Overdue), and due date. Closed or locked financial periods in Pegasus require manual reconciliation during scoping; we flag records belonging to locked periods and recommend the customer and accountant confirm period mapping before cutover.

Pegasus Media Campaigns aggregate real-time metrics, client meetings, and new projects. We extract campaign metadata and snapshot the current metrics state as static column values in a monday.com Board. Live data connectors do not transfer; metric values are point-in-time snapshots at migration. The customer recreates any live metric integrations (Google Analytics, Meta Ads, etc.) as monday.com integrations post-migration.

Pegasus holds assets, cash flow statements, and chart-of-accounts data at the finance layer. monday.com has no native financial module. We extract the accounts structure and balances, then present options to the customer: (a) import as read-only Items in a Finance Board, (b) export to a spreadsheet for accountant reference, or (c) integrate with a dedicated accounting tool post-migration. Historical transaction history within locked periods may require manual reconciliation; we flag this during scoping.

Pegasus user accounts with role information map to monday.com Team Members. We extract user records and map them by email match to the monday.com workspace. Active vs inactive status in Pegasus maps to Active vs Deactivated status in monday.com. Owner assignments on Jobs, Expenses, and Invoices migrate as Assignee column values on the corresponding Items.

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 a typed monday.com column (Text, Number, Date, Status, Dropdown, Checkbox, etc.). Custom field mapping is validated in the sandbox migration phase before production.

Documents and files attached to Jobs, Clients, or Invoices in Pegasus are extracted as binary blobs or URLs. We preserve attachment associations by mapping them to monday.com File columns on the corresponding Items, or to URL columns if the attachment is stored externally. Large binary files may require separate file storage coordination if the migration pipeline has size constraints.

Pegasus Standard and Enterprise tiers include workflow automation for routine tasks. monday.com's automation builder operates on different trigger-action logic. We do not migrate workflows as code. We extract and document every Pegasus automation rule (trigger, conditions, actions) as a written inventory with recommended monday.com automation equivalents. The customer's team rebuilds these in monday.com's automation builder post-migration.

Pegasus reporting module is consistently flagged as difficult to configure and inefficient on G2 reviews. monday.com dashboards with configurable widgets and chart views serve as the replacement. We do not migrate reports as code. We document every named report and dashboard configuration in Pegasus and deliver a written guide mapping them to monday.com dashboard equivalents. Chart view requires Pro tier at $33/seat per month.