Migrate from Output Time to Asana

Output Time Projects map directly to Asana Projects. We extract project name, description, status (active/archived), start date, end date, and project-level custom fields. The Asana project is created first as the container for all child tasks. Output Time project membership (team members assigned to a project) maps to Asana project membership, which we configure via the Asana API by adding each member to the projects team membership endpoint.

Output Time Tasks map to Asana Tasks. We preserve the task name, description (migrated as rich text notes in Asana), assignee (via email lookup to the Asana User table), due date, priority (mapped to Asana Custom Fields as a priority dropdown), and status. The parent Project GID is resolved at migration time to set the tasks workspace and project membership. Output Time task-level custom fields migrate to Asana Custom Fields on the task.

Output Time Subtasks map to Asana Subtasks under their parent Task. The parent-child relationship is preserved by resolving the Output Time parent_task_id to the corresponding Asana Task GID. We migrate subtask name, description, assignee, due date, and status. Any subtask with a missing or unresolvable parent is flagged in the reconciliation report and held for admin resolution.

Output Time Time Entries (date, duration in hours/minutes, billable flag, user, notes) do not have a native equivalent in Asana on Starter or Advanced tiers. We aggregate time entries by task and write the total hours as a custom numeric field on the task (e.g. Hours_Logged__c). The billable flag is written as a custom checkbox field (Is_Billable__c). Asana Business tier includes native time tracking; we document this as a post-migration configuration step for customers on Business.

Output Time Users (name, email, role, active/inactive status) map to Asana Users. We match by email address. Any Output Time user not found in the destination Asana workspace is held in the Owner reconciliation queue for the customer to provision. Inactive Output Time users are imported as inactive Asana users to preserve historical assignment records.

Output Time Clients are contact records associated with projects. We map them to Asana Project Collaborators (external guests with email invitations) or to Contacts in the destination CRM if Asana is connected to one. Client name and email migrate; any billing or address data in Output Time is written to a custom text property on the collaborator record.

Output Time Milestones (name, target date, associated project) map to Asana Milestones attached to the parent Project. Milestone ordering is preserved by sorting on the target date during import. Asana milestones do not have a description field natively, so we write the milestone name and any associated notes into the milestone notes section of the Asana API.

Output Time custom fields are key-value pairs per record with no enforced type. We attempt type inference from stored values (date strings to date fields, numeric strings to number fields, true/false to checkbox). Where inference is ambiguous or where the destination field type does not match the inferred type, we create a text custom field and flag the conflict in the pre-migration field map for the customer to review and correct post-migration.

Output Time Tags applied to tasks or projects are exported as string arrays and mapped to Asana Tags via the Asana Tags API. We create each unique tag in the destination workspace and attach it to the corresponding task GIDs. Tags used for categorization rather than collaboration (e.g. billing codes) are documented as a recommended Custom Field in Asana for better filtering and reporting.

Output Time stores file attachments on tasks and projects in its internal file system, but there is no API endpoint to download them. We do not migrate attachments. We produce an inventory of all attachment filenames, their parent task or project, and their original upload date. The customer re-uploads files to the corresponding Asana task manually post-migration using the file attachment feature in the Asana web UI or mobile app.

Output Time invoice records (line items, totals, status, client reference) are extracted as structured data where available. We produce a line-item summary CSV for manual invoice recreation. Asana does not have a native invoice object. If the customer uses Asana with a connected billing tool (QuickBooks, Xero), we document the recommended integration path and data mapping for the billing administrator to configure post-migration.

Output Time does not have a workflow automation engine. Any informal process or recurring task pattern used by the team is documented as part of the pre-migration process inventory. We deliver a written map of these patterns for the customer to rebuild as Asana Rules using Asanas automation builder (available on Starter+). This is an admin task, not a data migration deliverable.