Migrate from AceProject to Asana

AceProject Projects map directly to Asana Projects. The project name, description, status, start date, and due date transfer as standard Asana project fields. Custom project-level fields in AceProject map to Asana custom fields created on the project before migration. We preserve the project hierarchy if the account uses parent-child project grouping.

AceProject Tasks map to Asana Tasks within the corresponding project. Assignee, due date, start date, estimated hours, priority, status, and description transfer directly. Task description migrates as the Asana task description field. Custom task fields in AceProject (Boolean, Date, List, Numeric, Text, User types) require pre-creation of equivalent Asana custom fields; we create these before the task import phase and map values by field name.

AceProject Subtasks nested under Tasks map to Asana subtasks (tasks with a parent_task reference). We flatten the AceProject tree structure during export and reconstruct it in Asana using the parent Task GID as the parent reference. Nested subtasks (sub-subtasks) map to Asana subtasks with their direct parent as the parent_task.

AceProject Users map to Asana Users by email address. We export all user records including name, email, and user-level custom fields. Post-import, we add each migrated user to the corresponding Asana project as a member. Note: Asana's free tier restricts project member counts, so we flag the destination Asana plan during scoping if the project has more than 15 members on a free or Starter plan.

AceProject Task dependencies map to Asana Dependencies. We export the dependency type (finish-to-start, start-to-start, etc.) and the linked Task ID, then create Asana dependency records with the correct blocking and blocked task references. Teams should note that Asana has documented limitations where dragging a milestone task does not always cascade date changes correctly to all downstream dependent tasks.

AceProject Time Entries record hours, dates, billing rates, and task association. Asana has no native time tracking object in its core PM platform — time tracking requires the optional Asana Time Tracking add-on or a third-party integration. We migrate time entry data as a custom multi-value field (Date + Hours + Notes) on the corresponding task, or as a task note if custom fields are not preferred. The customer chooses the format during scoping.

AceProject Expense records include amount, category, currency, date, and task association. Asana has no native expense object. We migrate expense data as a custom multi-value field on the task or project, preserving amount, category, and date. Expense approval workflows and per diem rules do not migrate; these are documented as part of the automation inventory.

AceProject Documents store files attached to Projects or Tasks with version history. We export document metadata (filename, upload date, uploader, version) and file reference URLs. File content transfer depends on whether AceProject hosts the files or links to external storage. If files are hosted in AceProject, we download them and re-upload to Asana as project or task attachments. If AceProject links to external URLs, we preserve the URL as a link attachment.

AceProject task custom fields support Boolean, Date, List, Numeric, Text, and User types. These map to Asana custom fields of equivalent type. List fields become Asana Dropdown; Boolean becomes a Checkbox (custom field) or a single-select with Yes/No options. User-type fields in AceProject map to Asana People fields. All destination custom fields must exist in Asana before task import begins; we create them during the schema pre-creation phase.

AceProject User-level custom fields migrate as key-value pairs. Asana User profiles support custom fields in the Profile section. We map text, date, and list custom fields to their Asana equivalents. Numeric and Boolean fields map to Number and Checkbox user custom fields respectively. User custom fields in Asana are workspace-level and appear on all user profiles.

AceProject document and task Comments migrate to Asana task Comments. We export comment text, author, and timestamp. Comment threading in AceProject is flattened during migration — nested replies become top-level comments in Asana ordered by timestamp. Rich text formatting in AceProject comments is simplified to plain text or basic HTML-safe formatting in Asana comments.

AceProject email reminders and basic task notification workflows do not migrate as automation code. We audit every active workflow and email reminder configuration and document it as a written inventory with trigger, conditions, and action details. This inventory is handed to the customer for rebuild in Asana Rules (available at Premium and above) or Asana's advanced automation features. Workflow rebuild is outside standard migration scope.