Migrate from Monograph to monday Work Management

Monograph Projects map directly to monday.com Boards. The project name, description, start and end dates, and project status migrate as board name, description, and column values. Phase structures within Monograph projects map to Groups within the monday.com Board. Any project with open timesheet entries, pending invoices, or unbilled fees is flagged for sequenced migration (timesheets first, then invoices, then project closure) to avoid orphaned financial associations.

Monograph project phases map to Groups within the corresponding monday.com Board. Phase names, budget allocations, and status values migrate as Group properties and column values. Phase start and end dates map to timeline columns if the project uses the Pro plan's timeline feature.

Monograph timesheet entries (the most exportable object in Monograph's native API) map to monday.com Items with time-tracking column values. Each entry carries the staff member, date, hours, billable/non-billable flag, and project-phase association. We map billable entries to monday.com's time-tracking column format and non-billable entries to a separate numeric column. The Pro plan ($19/seat) includes time-tracking columns; Standard ($12/seat) does not, so we flag this during scoping if the customer's tier does not support it.

Monograph Invoices are generated from unbilled fee entries and linked to Projects and Clients. Since monday.com has no native invoicing, we offer two migration strategies during scoping: Option A maps invoice headers and line items to a structured set of columns on a dedicated finance board (Invoice Number, Client, Project, Amount, Status, Date), preserving the data but not the PDF. Option B exports invoices as structured CSV attachments on the project board and recommends a monday.com-integrated tool like PandaDoc or QBO for future invoice generation. Write-off records are mapped to a separate Status column value or a dedicated adjustment column.

Monograph Clients map to monday.com Contacts (available on Standard and above) with client-project linkage preserved through the integration between monday.com contacts and the project board. Client portal access settings from Monograph are noted as a custom property (client_portal_enabled__text) for manual rebuild in monday.com's sharing and guest-access settings post-migration.

Monograph Staff records (Principals, Project Managers, Staff) map to monday.com Users by email match. Role assignments, hourly rates, and PTO balances migrate as user properties. Note: monday.com's user model does not have a native PTO balance field, so we map PTO balances to a custom text property as a snapshot note and recommend the firm's admin rebuilds accrual tracking in monday.com's absence management or a separate HR tool.

Monograph project budgets are structured financial targets tied to phases or cost codes. Since monday.com has no native budget tracking, we map budget values to numeric columns (Budget_PhaseX) and create formula columns for variance calculations (Budget minus Actual). Over-budget flags and amendment history are preserved as status or text columns on the project board. The customer decides during scoping whether budget data migrates as live columns or as a one-time historical reference.

Monograph tracks unbilled fee write-offs as a separate decision record tied to projects. If write-offs are not migrated, the unbilled totals in the destination system will be inflated, leading to incorrect revenue reporting. We extract write-off decisions from project financial records and map them to a dedicated column (write_off_status or adjustment_amount) on the project board, so the firm's financial snapshot is preserved in monday.com even without native billing.

Monograph Workflows automate repetitive project tasks with trigger conditions and actions. monday.com has two automation layers: Automations (board-level if-then rules, available from Standard) and Workflows (workspace-level multi-step processes with branching and delays, available on Pro and Enterprise). We extract workflow definitions and trigger conditions and map them to the equivalent monday.com construct, but we do not migrate workflows as code. We deliver a written workflow inventory document that the firm's admin uses to rebuild in monday.com's automation builder.

Monograph tracks PTO and leave requests as a distinct object with balance tracking. monday.com does not have a native PTO module. We migrate PTO balances as a snapshot text property on the staff member's user profile and migrate leave request history to a separate Time Off board with item records per request. The firm's admin rebuilds accrual calculation logic post-migration since monday.com does not compute PTO automatically.

Monograph Custom Fields on Projects map to monday.com Custom Columns with equivalent data types where available (text to text, number to number, date to date). Fields without a direct monday.com equivalent (such as AEC-specific dropdowns for cost code categories) are mapped to text columns with the original values preserved. We flag any custom field that cannot be represented in monday.com's column type system during scoping.

Weekly Pulse (released Summer 2025) aggregates staffing, budget, and timeline changes into an ephemeral weekly digest. These are summary records with no underlying source data to migrate. We confirm with the customer during scoping that Weekly Pulse is informational only and does not need to be preserved.