Migrate from Monograph to Jira

Monograph Projects map directly to Jira Projects. Within each Jira Project, we create an Epic per Monograph phase structure to preserve budget phase associations. The Jira Project key (e.g., ARCH-101) is generated from the Monograph project name or client code during migration. Project status (active, on-hold, completed) maps to Jira Project workflow states, and any project-level custom fields (billing type, contract value, client tier) become Jira Project properties or custom fields on the Epic.

Monograph phases within a project map to Jira Epics. Each Epic inherits the parent Jira Project key and carries the phase budget value, start date, and end date as custom fields. Phases without a Monograph budget are created as Epics with zero-value budget fields. If a Monograph project has no phases, a single Epic named 'Project Scope' is created under the Jira Project to anchor any timesheet worklogs.

Monograph Clients map to Jira Organizations. We extract client name, primary contact, email, phone, and address, and import them as Jira Organization fields. Client portal access settings stored as custom properties in Monograph are flagged in the migration notes as requiring Jira Service Management or a Confluence-based client portal if the same visibility is needed in Jira. Client-project linkage is preserved via the Jira Project's Organization field.

Monograph staff records map to Jira User accounts. Role assignments (Principal, Project Manager, Staff) map to Jira Project Roles — we create the equivalent role names in Jira Projects before importing staff. Hourly rates from Monograph are preserved as a custom field on the Jira User record for time-tracking and budget calculations. Staff without Jira accounts are placed in a reconciliation queue; the customer's admin provisions the accounts before production migration.

Monograph timesheet entries map to Jira Issues (Story, Task, or Bug based on the work type in Monograph) with worklogs attached. We enable Jira's time tracking on each migrated Project before importing. Each Monograph timesheet entry becomes a Worklog with the original date, duration, billable flag, and description. The billable/non-billable flag from Monograph maps to Jira's billable worklog setting if the Jira instance has a time-tracking app installed; otherwise it is stored as a custom Issue field. Non-billable entries are logged without the billable flag.

Monograph Invoices have no native Jira equivalent. We preserve invoice data by mapping Invoice Number, Issue Date, Due Date, Line Items, Amount, and Payment Status as custom fields on the Jira Epic (for project-level invoices) or on the parent Issue. Invoice PDFs are attached as Jira Issue attachments to the corresponding Epic. Write-off records from Monograph are stored as a custom text field with a structured note (write-off reason, amount, date) on the Epic. Customers should evaluate whether they need an external invoicing tool (Jira Service Management billing add-on, FreshBooks, or QuickBooks integration) to replace Monograph's native invoice generation.

Monograph project budgets tied to phases map to Jira Epic custom fields. We create a numeric custom field budget_total__c, budget_spent__c (calculated from timesheet worklogs), and budget_remaining__c on each Epic. Any over-budget flags or amendment history are stored as a JSON-structured custom field budget_amendments__c on the Epic. Customers relying on Monograph's budget-vs-actual reporting should evaluate eazyBI or Power BI connectors for Jira to reproduce budget dashboards from migrated worklog data.

Monograph custom fields on Projects and Phases map to Jira custom fields of the equivalent data type. Text fields map to Jira Text fields, numeric fields to Number fields, date fields to Date fields, and multi-select fields to Jira Multi-select. Custom fields without a direct Jira equivalent (e.g., billing-tier dropdowns specific to Monograph) are mapped to Jira Select fields with the original values preserved as options. Custom field schema is deployed to Jira before any data import begins.

Monograph Workflows automate repetitive project tasks and cannot be migrated as Jira Automation rules because the trigger models differ fundamentally. Monograph uses project-task event triggers; Jira Automation uses Issue event, scheduled, and manual triggers. We extract every active Monograph Workflow definition (name, trigger, conditions, actions) and deliver it as a written inventory with a recommended Jira Automation or ScriptRunner equivalent for each rule. The customer's Jira admin or an Atlassian partner rebuilds the automations post-migration.

Monograph PTO balances and leave request records are extracted as a snapshot and preserved as a structured CSV with Staff ID, leave type, balance amount, and request dates. Jira has no native PTO tracking module. The CSV is handed off to the customer's HR team to import into their HRIS or to be reviewed against any PTO add-on in the Atlassian Marketplace. We do not attempt to model PTO as Jira Issues or custom fields.

Monograph's Weekly Pulse feature (released Summer 2025) generates ephemeral digest summaries aggregating staffing, budget, and timeline changes. These are derived records with no independent existence — they are regenerated from the underlying Project, Timesheet, and Budget data already migrated. We do not attempt to export or import Weekly Pulse records. Customers who rely on Weekly Pulse for reporting should configure Jira Dashboard gadgets or eazyBI to reproduce equivalent staffing and budget digest views from migrated data.