Migrate from Forecast to Asana

Forecast Projects map directly to Asana Projects. We export the project name, status, start date, end date, description, and any custom properties, then land them as Asana Projects. The Asana Team membership is set during migration based on the customer's org structure mapping provided during scoping. Completed projects in Forecast map to completed projects in Asana with the completed_at timestamp preserved.

Forecast Phases are mid-level groupings within a Project that chunk large work streams into named segments. We map Phases to Asana Sections within the corresponding Project, preserving the phase name, sequence order, and any phase-level custom field values. If a Forecast project has no Phases, we create a default Section to hold all migrated Tasks.

Forecast Tasks map 1:1 to Asana Tasks. We transfer task name, description (as rich text), status (mapped to Asana completion), assignee (resolved via email to Asana User), due date, and start date. Subtasks in Forecast map to subtasks in Asana, preserving the parent-child relationship. The Task ID from Forecast is stored in a custom field fc_original_id__c for audit and cross-reference.

Forecast Milestones are standalone objects with a name, target date, and parent project reference. Asana does not have a native Milestone object; we implement milestones as Asana Tasks with the milestone flag set (or as pinned deadline tasks if the destination is on Starter tier without the milestone feature). We preserve the milestone name, target date, and project association. The milestone status (achieved, missed, upcoming) is stored as a custom field on the migrated task.

Forecast custom fields applied at the Project level migrate to Asana local custom fields scoped to the corresponding project. Text fields map to Asana text custom fields, numeric fields to number fields, and choice fields to enum custom fields with option lists recreated. If the customer requests global availability, we create Asana organization-level custom fields and apply them to the migrated projects post-import.

Forecast custom fields applied at the Phase level map to Asana local custom fields on the project containing the corresponding Section. Phase-level custom field values are stored as Section metadata in a custom field section_custom__c on each task belonging to that phase, since Asana Sections do not support custom fields natively.

Forecast task-level custom fields map directly to Asana task custom fields. We identify every distinct custom field name and type across all Forecast tasks during scoping, then pre-create the corresponding Asana custom fields (local or global based on customer preference) before migration begins. Choice options are reproduced verbatim; numeric precision is preserved.

Forecast custom fields attached to Time Registrations cannot map to Asana task custom fields because Asana tasks do not store time entry metadata natively. We export the time registration custom field values alongside the Time Registration itself and store them in a custom field fc_time_registration_meta__c on the linked task as JSON-serialized metadata, or flag them for the customer's admin to review in a post-migration reconciliation report.

Forecast Time Registrations carry hours, date, billable flag, and optionally a rate, linked to a Task. Asana has no native billing rate model. On Asana Advanced plans ($24.99/user/month), native time tracking stores hours and dates per task but not billing rates. We migrate hours and dates as Asana time entries where available, and store the billable flag and rate as custom fields on the task (fc_billable__c, fc_hourly_rate__c). The customer assigns a time-tracking integration (Harvest, Toggl) if ongoing billing-grade time capture is required.

Forecast Rate Cards define hourly billing rates per role or person. Asana has no rate card concept. We export the rate card structure (role name, rate amount, effective dates) and create Asana organization-level number custom fields for each role (e.g., fc_rate_senior_pm__c, fc_rate_junior_dev__c). Rate values are static metadata for reference; they do not auto-apply to time entries in Asana. We note in the handoff document that the customer should configure their chosen time-tracking integration to reference these rates if billing automation is needed.

Forecast assigns team members to tasks with an allocation percentage or hours. Asana Workload view (Advanced plan) shows capacity but does not store per-task allocation percentages as records. We extract assignment percentages and store them as custom number fields on each migrated task (fc_allocation_pct__c). We also produce a CSV inventory of all resource assignments for the customer's admin to configure in the Asana Workload view post-migration. Assignments where the Forecast user has no Asana User counterpart go to a reconciliation queue.

Forecast Users referenced on any record (assignee, time registration owner, resource assignment owner) are matched to Asana Users by email address. We extract every distinct user reference across all objects and produce a User mapping table. Any Forecast user without a matching Asana User goes to a reconciliation queue for the customer's admin to provision before record import resumes. User names, email addresses, and active/inactive status are preserved.

Forecast's Project Health or status update feature (green/amber/red indicators) has no direct Asana equivalent. We capture the last known status value and project-level notes and store them in a custom text field fc_project_status__c on the Asana Project description or as a pinned task note for the customer's PM to reference.

Forecast task attachments migrate to Asana task attachments via the Asana API. We flag any attachment exceeding 100 MB as a gotcha item, since Asana's API does not accept attachments over that size. The customer's admin receives a list of oversized attachments with URLs to re-upload manually post-migration.