Migrate from Monograph to Trello

Monograph Projects map to Trello Boards. The project name becomes the board title; the project description and phase structure migrate as board descriptions and Lists representing each project phase or billing milestone. Project status (Active, On Hold, Completed) maps to the board visibility setting or a project status label on all cards. Trello does not support project-level financial targets, so budget and fee-expended data are stored in a named CSV attachment or as a board description field for reference. Monograph's client-project linkage is preserved as a board membership entry for the mapped client.

Monograph Client records map to Trello Workspace members. Company name becomes the member display name; primary contact email and phone migrate as custom fields on a designated reference card or as a board description note. Client portal access settings (Monograph-specific) have no Trello equivalent and are documented as a property mapping note for the customer's admin to configure manually in the Workspace settings. Clients with multiple contacts require the admin to decide whether to create one workspace member per contact or consolidate under a single company member.

Monograph Staff records (Principal, Project Manager, Staff role) map to Trello Workspace members. Role assignments have no native Trello equivalent, so we store the original Monograph role in a text custom field on each member's profile card or as a board note. Hourly rates migrate to a number custom field on the member card for reference during timesheet reconciliation. Staff with inactive status in Monograph are migrated as deactivated Trello workspace members, pending the admin's decision to remove or retain access.

Monograph Timesheet entries map to Trello Cards, one card per timesheet record. We create a dedicated board or a tracker list within each project board to hold timesheet cards. Card title uses the project and date; hours, billable flag, and description migrate as Trello custom fields (number for hours, checkbox for billable, text for notes). Trello has no native timesheet object, so the custom field approach is a workaround that preserves the data but requires the team to interact with cards rather than a dedicated timesheet view. Firms with high timesheet volume may prefer to export timesheets as a separate CSV reference file rather than individual cards.

Monograph project phases map to Trello Lists within the corresponding board. Phase name becomes the list title; phase-level budget and fee-expended values migrate as a structured attachment on the board or as list description fields. Over-budget flags are stored as labels on all cards within the affected list. The phase sequence order is preserved by ordering the lists from left to right in the original phase sequence.

Monograph project budgets stored as phase-level or cost-code financial targets have no direct Trello object. We create number custom fields on a budget reference card (one per project board) that holds all budget line items, or we attach a structured CSV summarizing the budget data. The admin decides whether to use a dedicated budget reference card or a separate budget board with one card per budget line. Over-budget flags and amendment history migrate as label tags or attachment notes on the budget reference card.

Monograph Invoices with headers, line items, payment status, and write-off records have no native Trello representation. We attach each invoice as a PDF to the corresponding project board's budget reference card, or we export a structured invoice CSV (invoice ID, client, project, amount, status, write-off amount) as a board attachment for the customer's admin to reconcile against their accounting software. This is an explicit limitation that requires the customer to maintain invoice history in their accounting tool post-migration.

Monograph Workflows (automation triggers and conditions) do not migrate as Trello Butler rules because they are structurally different automation models. We extract each workflow definition with its trigger, conditions, and actions into a written inventory document. The customer's admin uses this document to rebuild equivalent Butler rules or Power-Up automations in Trello post-migration. We do not configure Butler rules as part of the migration scope.

Monograph PTO balances and leave request records migrate as a structured CSV or as a dedicated Trello board with one card per leave record. Trello has no native PTO tracking module, so balance calculations require a separate tool or manual reconciliation. We document the PTO balance snapshot as a note on each staff member card and recommend a parallel-run period for leave tracking post-migration to account for accrual method differences.

Monograph custom fields on Projects and other objects map to Trello custom fields by type: text fields to Trello text, numbers to Trello number, dates to Trello date, and dropdowns to Trello dropdown. We create the Trello custom field definitions on the destination board before importing any card data. Custom field types that cannot be exactly matched (for example, a Monograph currency field without a Trello currency equivalent) are mapped to the closest Trello type and documented in the mapping reference.

Monograph unbilled fee write-offs tracked as separate project financial decisions must be preserved for billing accuracy. We create a label called Write-off on each affected project board and tag the corresponding budget reference card with the label and the write-off amount and reason as a card comment. Without this step, the unbilled totals in the customer's accounting tool will be inflated, leading to incorrect revenue reporting. This is a high-severity mapping item that we explicitly verify during reconciliation.

Trello's native export does not include archived cards by default. If the destination Trello workspace has archived cards from prior use that need to coexist with migrated Monograph data, the admin must manually unarchive them before the export runs. We flag this in the pre-migration checklist and verify that all archived cards have been restored before production migration begins. This limitation is specific to the Trello destination and does not apply when migrating to other platforms.