Migrate from Monograph to Asana

Monograph Projects map directly to Asana Projects. We preserve the project name, phase structure, timeline (start and end dates), budget targets, and staff assignments. In-progress projects require special sequencing: timesheet data migrates first, invoice history second, then the project record last to avoid orphaned financial associations. Any project with open unbilled fees requires the unbilled total preserved as a custom field on the Asana project record.

Monograph Clients with a dedicated portal association map to Asana Teams for internal use. Client contact records (name, email, company) migrate as custom properties on the project record (client_name__c, client_email__c) since Asana has no native client account object. Client portal access settings from Monograph are preserved as a note in the custom properties; guest access in Asana must be reconfigured post-migration by the admin.

Monograph time entries migrate to Asana Tasks with custom numeric fields capturing hours worked (hours__c), billable/non-billable flag (billable__c as a checkbox), and date worked. The task title reflects the work description from the timesheet entry. We preserve the original Monograph timesheet period grouping by creating a parent subtask or section for each pay period. Historical timesheet totals per project migrate as rollup fields documented on the project record.

Monograph Invoices do not have a native Asana equivalent. We migrate invoice headers (invoice number, date, client, amount, status) as structured custom fields on the associated project record, and attach a PDF summary of the invoice as a task attachment where Asana's file attachment limit (100MB per file) applies. Payment status and write-off decisions migrate as custom field values (invoice_status__c, write_off_amount__c). Customers who need full invoice history accessible inside Asana receive a consolidated invoice summary attachment per project.

Monograph tracks unbilled fee write-offs as separate decision records tied to projects. If write-offs are not migrated, the unbilled totals in any financial reporting derived from the Asana project records will be inflated. We extract write-off decisions from project financial records and map them to a write_off_amount__c custom field and a write_off_reason__c text field on the project record, preserving the decision for revenue reconciliation.

Monograph Staff records (name, email, role assignment, hourly rate) map to Asana Users. Role assignments (Principal, Project Manager, Staff) migrate as Asana membership roles within the Team. Hourly rate values migrate to a custom field (hourly_rate__c) on the User profile. Any Monograph Staff record with a deactivated status migrates as an inactive Asana User to preserve historical assignment data.

Monograph project budgets (budget amounts per phase or cost code) migrate as custom numeric fields on the Asana Project (budget_total__c, budget_phase_1__c, budget_phase_2__c, etc.). Over-budget flags and budget amendment history are preserved as a text field (budget_amendment_history__c) documenting the original and revised amounts with dates. Asana does not support native budget tracking; any budget-vs-actual reporting requires post-migration configuration of a reporting tool or spreadsheet against the migrated data.

Monograph Workflow definitions (trigger conditions, automated actions, task assignments) are extracted and documented in a written Workflow Inventory delivered to the customer's admin. We do not migrate Workflows as executable code because Monograph and Asana automation models differ structurally. The inventory includes the workflow name, trigger type, conditions, and recommended Asana Rules equivalent for the admin to rebuild.

Monograph PTO balances and leave request records migrate as a snapshot in a custom field on the Asana User record (pto_balance_snapshot__c) along with the snapshot date. Asana's workload management tracks capacity but not PTO accrual balances. We recommend a parallel-run period for PTO tracking post-migration where the HR or finance team reconciles the snapshot balance against the destination system's accrual calculation (front-loaded vs. accrual-based) before closing out the Monograph source.

Monograph custom fields on Projects and other objects migrate to Asana custom fields of equivalent type (text, number, date, dropdown). Dropdown field options map to Asana enumerations. Any custom field without a direct Asana type equivalent is flagged during scoping and the customer chooses whether to map to the closest available type or preserve as a text field.

Monograph Weekly Pulse (released Summer 2025) generates ephemeral digest summaries aggregating staffing, budget, and timeline changes into weekly snapshots. These are not exportable data records and do not migrate. We document the feature's existence and its data sources (staffing board, budget view, timeline view) so the customer understands which live views in Asana reproduce the same information.

File attachments linked to Monograph Projects or Tasks migrate as Asana Attachments via the Asana API. Attachments exceeding 100MB are flagged and excluded from migration; the customer receives a list of oversized files with the option to split or store externally. Image attachments migrate fully; PDF reports are migrated but Asana renders them inline rather than in the export-only single-page format available in Monograph.