Migrate from Trigger to Asana

Trigger Clients map to Asana Teams, which serve as the organisational unit for each client relationship. We extract the client slug or name and create a corresponding Asana Team, preserving the client email domain as a naming reference. User membership in the Asana Team maps to the list of Trigger users who were assigned to that client's projects. Projects and tasks in Trigger are imported as Asana Projects and Tasks belonging to the corresponding Team, providing the project-to-client linkage that Trigger maintains natively.

Trigger Projects map directly to Asana Projects. The project name, status (active, archived), start and due dates, project manager assignment, and hourly budget cap migrate as typed fields. The Trigger client association maps to the Asana Team membership, so the project appears under the correct Team. Archived or locked projects are flagged during scoping and imported as inactive Asana projects with a status custom field to preserve the audit trail without cluttering active workspaces.

Trigger Tasks map to Asana Tasks with name, assignee (resolved by email to the Asana User), priority, status, due date, and estimated hours preserved. Subtasks are nested under their parent task in Trigger; we extract the full hierarchy during the CSV export phase and reconstruct parent-child relationships in Asana using subtask nesting. Trigger task sections map to Asana Sections within the project, maintaining the grouping logic that teams rely on for work organisation.

Trigger subtasks nested under tasks are extracted as discrete records during the CSV join phase and imported as native Asana subtasks under their parent task. The parent task GID is resolved at import time so that the subtask-to-parent relationship is established immediately on insert rather than requiring a second pass. Assignee, due date, priority, and estimated hours on the subtask carry over, and any custom fields applied to the subtask in Trigger are created in Asana before the subtask import phase begins.

Asana has no native time-tracking object, so Trigger time entries require a configuration workaround. We create a dedicated Asana project named 'Time Logs' with custom fields for duration (number), entry date (date), billable flag (checkbox), associated project (text lookup), and associated task (text lookup). Each Trigger time entry becomes a Task in this project with the custom fields populated. Billable time entries in Trigger also link to a Trigger Invoice; we document the total billable amount and associate it with the original project as a note for the customer's team to reconcile in Asana's workload view or a connected billing tool.

Trigger invoices are derived objects: the line items are computed from billable time entries rather than stored as discrete records. Asana has no native invoicing or billing feature at any pricing tier. We do not create invoice records in Asana because there is no target object. Instead, we extract invoice metadata (client, project, total amount, status, and date) and invoice line items (derived from billable time entries) and deliver them as a structured CSV inventory. The customer reviews this inventory during the handoff and rebuilds invoices in their preferred billing tool (QuickBooks, FreshBooks, or a custom Asana-connected workflow) using the CSV as a reference. This limitation is documented in the Scope section of the migration agreement before work begins.

Trigger Users map to Asana Users by email address, which serves as the dedupe key for owner resolution. The Trigger role (admin or member) maps to Asana team membership and permission level: admin users are granted Team Admin in their respective Asana Teams. The hourly rate from Trigger migrates as a custom field on the Asana User profile for use in project budget calculations or time-tracking reconciliation. Any Trigger user without a matching email in the destination Asana organisation is held in a reconciliation queue for the customer's admin to provision the account before record import resumes.

Trigger custom fields on projects and tasks are exported with their field definitions and values. We create the corresponding custom fields in Asana before any data import, matching field types (text, number, date, single-select, multi-select, checkbox) as closely as possible. Trigger formula fields, conditional fields, and rollup calculations have no direct Asana equivalent and are flagged during scoping; we document the field definition and its output value as a static text custom field in Asana so the historical value is preserved even if the calculation logic cannot be replicated.

Trigger project sections grouping tasks within a project map directly to Asana Sections within the corresponding project. Section names, ordering, and the task membership within each section carry over as part of the task import phase. Trigger's section-level project manager assignment is not a native Asana concept; we document it as a custom field note in the migration handoff if it was actively used.

Trigger task comments export from the task CSV view and map to Asana Task Stories, preserving the comment text, author (resolved by email to Asana User), and timestamp. Comment ordering is preserved by setting the created_at timestamp on the Asana story to match the original Trigger comment date. Any rich text formatting in Trigger comments that is not natively supported in Asana Stories is simplified to plain text during the import phase to prevent rendering issues.

Trigger file attachments stored within tasks and projects are not accessible via a public API. We extract the file names, URLs, and associated task or project references from the Trigger export CSVs and deliver a written file inventory. The customer downloads each file from Trigger manually (or using a browser-based bulk download if available) and re-uploads them to the corresponding Asana task or project. Any file exceeding Asana's 100MB per-attachment limit is flagged in the inventory for manual handling. This limitation is disclosed in the pre-migration scoping call and documented in the handoff report.

Trigger user roles (admin or member) and hourly rates are separate from the core user record. Admin status in Trigger maps to the Team Admin permission in the corresponding Asana Team; standard members map to Member. The hourly rate migrates as a number custom field on the Asana User profile named 'Hourly Rate (from Trigger)' for use in budget tracking or billing reconciliation. Rate values are preserved as numeric floats to two decimal places.