Migrate from Trigger to monday Work Management

Trigger Clients (name, email, billing address, optional currency setting) map to monday.com contacts either via the monday CRM Contacts feature (if CRM is installed) or via a dedicated Client board with a People column for contacts and a text/address column for billing details. We map the billing address to monday's address column type, but flag any Client records missing a billing address before import so the customer can decide whether to leave the field blank or populate manually. Currency settings in Trigger become a label field on the Client board with no automatic currency conversion at import.

Trigger Projects (client association, project manager, status, start/due dates, hourly budget cap) map to monday.com Boards. We map the project manager assignment to a People column, status to a Status column with matching values, dates to Timeline columns (Start Date and End Date), and budget cap to a Numbers column. The client association maps to a Connect Boards column (Pro+) or a link item column if the client is managed in a separate board. Teams with fewer than 5-10 active projects sometimes consolidate into a single Board with Groups per project rather than one Board per project, which we discuss during scoping.

Trigger Tasks (assignee, priority, status, due date, estimated hours, parent task for subtasks) map to monday.com Items. We map priority to a Labels or Priority column type, status to a Status column with values matching Trigger's task statuses, due date to a Date column, and estimated hours to a Numbers column. Trigger's subtasks become monday.com Subitems (Pro+ required) if the customer's plan supports it; if the customer is on Standard, we flatten the subtask into the parent Item's description or move it to a separate sub-board linked via Connect Boards column. We flag any custom fields on Trigger tasks before migration and pre-create equivalent column types in monday.com.

Trigger Time Entries (user, task, duration, date, billable flag) require a destination mapping decision. monday.com's native time tracking (Standard+) attaches to individual board items via a Time Tracking column rather than storing time entries as standalone records. For migrations where historical time data needs to be queryable across all projects, we create a master Time Entries board with Items representing each time log, linking back to the relevant project and task Items via Connect Boards columns. For migrations where only recent time data matters, we use monday.com's native Time Tracking column on the project board and import the most recent entries manually. We remap Trigger user IDs to monday.com team members before import to ensure assignee resolution.

Trigger Invoices do not store line items as discrete records — amounts are computed from billable time entries. We export invoice totals and the underlying billable time entries separately, then reconstruct the relationship by importing time entries first (as described above) and creating a client-side invoice record referencing those entries. monday.com has no native project invoicing module; we recommend either establishing a simple Invoice board with Items representing each invoice linked to the client and project boards, or using an external tool (Stripe, QuickBooks, FreshBooks) post-migration. We document the invoice mapping strategy and flag any gaps in Trigger's invoice data (missing client references, inconsistent billing addresses) before import.

Trigger Users (name, email, role, hourly rate) map to monday.com Workspace members. We export the full user list, match by email, and map role (admin or member) to monday.com permission tiers. Trigger's hourly rate is carried as a custom Numbers column on the user's profile board or on a dedicated Team Info board if the customer wants to preserve rate data for project budgeting. Any Trigger user who is not yet provisioned in monday.com goes to a reconciliation queue for the customer's admin to create before record import proceeds.

Trigger allows custom fields on projects. We export the field definitions (name, type, values) alongside the project records. Before data import, we create equivalent column types in monday.com on each project board — text, number, date, label, dropdown, or checkbox depending on the Trigger field type. monday.com's custom field types include dependencies (non-nullable in the new sentence infrastructure), which we document if the customer uses conditional field logic in Trigger.

Trigger custom fields on tasks follow the same pre-creation workflow as project custom fields. We export the field schema, map Trigger field types to monday.com column equivalents, create the columns on the destination boards before data import, then populate values as part of the standard item migration. monday.com's custom column types (text, number, date, label, dropdown, checkbox, rating, formula, etc.) cover the majority of Trigger's custom field use cases without requiring the customer to upgrade for column functionality.

Trigger file attachments stored within tasks or projects are not accessible via any documented API or export path. We do not migrate attachments as part of the standard migration scope. Customers should download files manually from Trigger's UI before the migration window or use a separate file migration tool for attachments. We flag the attachment gap in the discovery report so the customer can plan accordingly.

The billing address field in Trigger is optional and many client records were created without it. We export the full client list and flag any record missing a billing address. During monday.com import, records without a billing address land with an empty address field. We present this as a pre-import reconciliation item and let the customer's admin decide whether to populate the addresses manually post-migration or accept the blank fields.

Trigger's project hourly budget cap maps to a Numbers column on the monday.com project board. On Enterprise plans, monday.com's native Budget App provides variance tracking against actual time logged, which requires Pro+ time tracking to be meaningful. We map the budget value and note whether the customer wants to activate monday.com's Budget App post-migration as a separate configuration step.

Trigger's nested subtask structure requires a destination decision based on the customer's monday.com plan. Subitems are available on Pro+ plans and allow true subtask nesting under a parent item. On Standard plans, we flatten the hierarchy by creating separate Items for subtasks within the same Group and optionally linking them via a text field or Connect Boards column. We confirm the customer's plan tier before designing the subtask migration strategy and document the approach in the scoping report.