Migrate from Trigger to Trello

Trigger Client records map to Trello Boards. The client's name becomes the board title; the client's email and billing address are stored in the board description (as structured text since Trello has no native client object). We preserve the client's currency setting and optional billing address in custom fields on the board. The board is created first so that subsequent project-list imports can reference it as the parent context.

If the customer uses Trello Workspaces to separate business units or client groupings, we map Trigger Clients to Trello Workspaces by matching the client's industry tag or team assignment to the workspace name. The workspace is a lookup context layer above the board, not a direct record import.

Trigger Project records map to Trello Lists within the board created from the parent Client. The project name becomes the List name; project start/due dates are stored as custom date fields on the first card in the list or as board labels. Project manager assignment is preserved as a card label (team member assigned as project lead) rather than a native Trello field.

Trigger Task records map directly to Trello Cards. Task name becomes card title; task description migrates as card description; task priority maps to card label color (red for high, yellow for medium, green for low); task due date maps to card due date. Subtasks in Trigger are flattened as a checklist within the parent card. We preserve the subtask hierarchy by numbering checklist items to maintain ordering context.

Task status (Open, In Progress, Completed) in Trigger maps to a combination of card position within the list and a status label. Trello has no native status field outside of list position; we configure the target list structure (e.g., To Do, In Progress, Review, Done) during board setup to match Trigger's project workflow states.

Trigger Time Entry records link to a task and carry duration in minutes, a billable flag, and an optional hourly rate. We aggregate total minutes per task and store the sum as a custom numeric field on the Trello Card (e.g., 'Hours Logged: 4.5'). Individual time entry records are not recreated as separate cards; the aggregate provides the billable-hours context. Customers using a Trello Power-Up for time tracking (e.g., Placid or TrackSprint) can use the stored value to back-populate the Power-Up post-migration.

The billable flag on time entries maps to a Trello custom field 'Billable' (checkbox type if the Power-Up supports it, or a text label indicating Yes/No). The hourly rate from the Trigger user record is stored as a separate custom field 'Hourly Rate' on the card. The product of hours and rate is documented in the invoice inventory for manual calculation.

Trigger Invoices are not standalone stored objects but computed from billable time entries. We export each Trigger invoice (client, date, total amount, status) as a structured CSV and create a written invoice inventory that maps each invoice to the client board and the time entries it references. We do not create an invoice object in Trello because Trello has no native invoice capability. The inventory is delivered as a spreadsheet for the customer to import into a Trello-compatible invoicing Power-Up (e.g., Invoice Ninja integration, or manual entry into QuickBooks, FreshBooks, or Xero).

Trigger User records (name, email, role, hourly rate) map to Trello Board Members. We match by email address. Trigger's admin role maps to Trello board Admin; member maps to Normal. Hourly rate is stored as a custom field on any card where the user is the assignee. Users without a Trello account are added as observers or held in a reconciliation queue for the admin to provision.

User access to multiple client boards is managed through Trello Workspace membership. We add each Trigger user to the workspace corresponding to their team assignment. Board-specific access is managed at the board level for clients requiring restricted visibility.

Trigger's hourly project budget cap is stored as a custom numeric field on the first card of the project's list (or as a board-level custom field). We do not enforce budget tracking in Trello; the budget value is preserved as a reference figure for the customer's project manager.

Trigger custom fields on tasks (text, number, date, dropdown) map to Trello Card Custom Fields using the Custom Fields Power-Up. Field definitions are created on each board before card import. Trello's API returns empty values for dropdown custom fields in some integration contexts; we validate and patch affected cards post-import. Text and number fields transfer without known compatibility issues.

Trigger custom fields defined at the project level map to Trello Board Custom Fields. These are accessible on all cards within the board and apply the same type-mapped field creation process as task-level custom fields.

Trigger archived projects and tasks are migrated to a dedicated 'Archived' board in Trello with archived cards to preserve the record without cluttering active boards. Locked records are flagged in the reconciliation report for the customer to handle manually since Trello has no record-locking equivalent.