Migrate from Pegasus Systems to Jira

Pegasus Jobs (the project-level container with timelines, task lists, and resource allocation) map to Jira Software Projects. We extract the job name, status, start and end dates, and custom fields, then create a corresponding Jira Project with a Project Key derived from the Pegasus Job code or name prefix. Jira does not support hierarchical projects natively; if the Pegasus instance uses nested job structures, we map parent jobs to Jira Epics and child jobs to Stories within the Epic.

Pegasus Client records (contact information, campaign history, performance analytics) do not have a direct Jira equivalent because Jira is issue-centric rather than client-centric. We extract the primary client name and contact fields and store them in the Jira Project description or as a custom field (Client Name, Client Contact Email) on the project. The customer's Jira admin can optionally create a separate Client register as a Jira Service Management project if client-facing tracking is required after migration.

Pegasus per-minute timesheet entries (with billable/non-billable flags, project association, user assignment, and date) map to Jira Issue work logs. The billable flag from Pegasus maps to a Jira custom field (Billable: Yes/No) since Jira's native work log does not have a billable flag at all tiers. Non-billable time is logged as standard work log entries without the billable custom field set. We set the Jira Worklog Author to the Jira User matched by email from the Pegasus user record.

Pegasus Expense records (vendor, amount, date, job association, Accounts Payable data) have no native Jira equivalent. We offer two migration strategies: (1) snapshot strategy, where expenses are exported to a CSV and attached as a file to the relevant Jira Project, and (2) custom field strategy, where we create Jira custom fields (Expense Vendor, Expense Amount, Expense Date) and migrate expense records as Jira Issues of a dedicated Expense issue type. The customer chooses during scoping.

Pegasus Invoice records (headers, line items, amounts, payment status, closed/locked period flags) cannot be migrated as live billing records because Jira has no invoice object. We export invoices as PDF snapshots or structured CSV files and attach them to the related Jira Project. For customers requiring invoice data in Jira, we create a custom Invoice object in Jira with fields for invoice number, client, amount, date, status, and locked period flag. We flag any invoices in Pegasus locked financial periods separately for manual reconciliation.

Pegasus Media Campaigns aggregate real-time metrics, client meetings, and new projects. We extract campaign metadata (name, dates, client association, current metric snapshot) and create a Jira Project with a campaign summary stored in the Project description and current metrics stored as custom fields. Live data connectors are not recreated; the metrics are migrated as a static snapshot at cutover time. Jira admins can configure third-party analytics integrations post-migration if ongoing metric syncing is required.

Pegasus custom fields on Jobs, Clients, and other objects are documented during discovery and mapped to Jira custom fields of equivalent type. Jira supports text, number, date, single-select, multi-select, URL, user picker, and other field types. We create Jira custom fields in the target project context (not globally, to avoid consuming the org-wide custom field limit) before migration begins. Custom field names are preserved from Pegasus where they do not conflict with Jira reserved field names.

Documents and files attached to Pegasus Jobs, Clients, or Invoices are extracted as binary blobs or URLs and uploaded to the corresponding Jira Project or Issue. Large binary blobs (over 10 MB per file) may exceed Jira's default attachment size limit on some plans; we flag these during scoping and compress or split them as needed. Attachment associations are preserved by linking each file to the Jira Issue representing the Pegasus record it was originally attached to.

Pegasus user accounts map to Jira Users by email address match. We extract user records with role information from Pegasus and map them to Jira's product roles (Administrator, Member, Viewer). Active vs inactive status is preserved; inactive Pegasus users are provisioned as inactive Jira users so that historical assignment and work log attribution is not broken. Jira Cloud requires each user to have an Atlassian account, so any Pegasus users without email addresses require manual account creation before migration.

Pegasus financial records (assets, cash flow statements, chart of accounts, locked period data) are complex and tied to Pegasus's finance layer in ways that do not map to Jira's issue-centric model. We extract the accounts structure and current balances as a structured CSV for the customer's finance team to reconcile. Full historical transaction detail is excluded from migration unless the customer specifically requires it and has a custom financial records object configured in Jira. We flag locked-period transactions separately for the customer's accountant to review.