Migrate from ActionPlanner to Asana

ActionPlanner Objectives are the top-level strategic container holding KPIs, Initiatives, Milestones, and Actions. We extract title, description, ownership, start date, target date, and status and map them to Asana Goal using the Goals API. Parent-child linkage between Objectives and their child Initiatives is preserved as a goal relationship field in the migration payload so the relationship can be rebuilt in Asana Goals.

ActionPlanner KPIs are numeric or percentage-based performance indicators attached to Objectives. Their format and calculation logic vary between instances. We extract KPI name, target value, current value, and measurement unit and map them to Asana custom number or formula fields on the corresponding Goal. If the customer uses Asana Business or Enterprise, formula fields can compute progress percentages natively. The KPI calculation logic itself (a formula or manual entry in ActionPlanner) is preserved as a text note on the custom field.

ActionPlanner Initiatives are mid-level work packages that sit between Objectives and Milestones. Each has a title, description, owner, purpose statement, deadline, and child milestones. We extract all initiative fields and map them to Asana Project records. The parent Objective linkage is preserved via a custom project field (initiative_parent_objective__c) so the customer's admin can attach the Project to the corresponding Asana Goal after migration.

ActionPlanner Milestones are time-bound checkpoints within an Initiative. We extract title, due date, status, assigned owner, and the parent-initiative linkage and map them to Asana Milestone records. Asana Milestones are a task with the milestone checkbox enabled. We set the due date and title from ActionPlanner and link the milestone task to the parent Project derived from the parent Initiative.

Actions are the atomic execution unit in ActionPlanner — specific to-dos with a deadline, assignee, status, description, and parent milestone or initiative linkage. We extract every action field and map them to Asana Tasks. The parent-link field (parent_milestone__c or parent_initiative__c) is included in the migration payload for manual hierarchy reconstruction. If the customer uses Asana subtasks, deeply nested action chains can be represented as a parent task with child subtasks.

ActionPlanner Roadmaps are the top-level container for each strategic plan. The TEAM plan is limited to one roadmap; TEAM+ and CORPORATE allow multiple. We map each ActionPlanner Roadmap to a separate Asana Team within the destination Workspace. If the customer is consolidating multiple roadmaps into a single destination, we flag the plan tier required and confirm whether multiple Teams or a single Team with project folders is preferred before migration.

ActionPlanner assigns owners to Objectives, Initiatives, Milestones, and Actions. User names and email addresses are extracted from the export. We match owners by email against the Asana destination organization's User table. Any ActionPlanner owner without a matching Asana User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission hierarchies from ActionPlanner are flat in the export and cannot be migrated; we document the original role assignments for manual reconfiguration in Asana.

ActionPlanner status values (for example: Not Started, In Progress, At Risk, Complete) are extracted and mapped to Asana custom single-select fields on the relevant task type. If the customer uses Asana's built-in task status icons (On Track, At Risk, Off Track), we configure those instead. Status color coding from ActionPlanner is preserved as field options in the destination.

File attachments linked to Actions or Initiatives are extracted from the export package and uploaded to the corresponding Asana Tasks or Projects via the Asana Attachments API. We preserve the original filename, file type, and upload timestamp. If any attachment exceeds Asana's 100MB per-file limit, we flag it for manual handling.

ActionPlanner supports collaborative decision logging and discussion threads around plans and actions. The platform does not expose a documented export for conversation history or decision logs. We flag this limitation in the migration scope and document the expected data loss for the customer before proceeding. We do not fabricate or reconstruct comment history. If the customer requires a record of decision history, we recommend exporting ActionPlanner's decision logs manually before the migration window and attaching them as PDFs to the relevant Asana Goals or Projects.

ActionPlanner instances may include custom fields on Objectives, Initiatives, Milestones, or Actions. We extract all custom field definitions (name, data type, options) and map them to equivalent Asana custom field types: text fields, number fields, date fields, single-select, multi-select, or people fields. Custom field values are migrated as part of the record import. Some ActionPlanner custom field types (for example, formula or calculation fields) have no direct Asana equivalent and are preserved as text fields with a note indicating the original field type.

If ActionPlanner stores internal notes or activity entries linked to Actions, we extract those as Asana Story records (using the stories API on the task) or as Note records attached to the parent task. We set the author from the owner mapping and the timestamp from the original engagement date. This migration is only possible if ActionPlanner exposes engagement or note data in the vendor-assisted export.