Migrate from Cobalt Project Manager to Asana

Cobalt Projects map directly to Asana Projects. Project name, description, start date, and end date migrate as Project Name, Notes, and Start Date / Due Date fields. We set the Asana project privacy (public or private) based on the Cobalt project's visibility flag. Projects are loaded first in the migration sequence because every Task references a parent Project.

Cobalt Tasks map to Asana Tasks attached to the parent Project. Task name, description, start date, due date, priority, and status migrate directly. The Cobalt Task status values (not started, in progress, complete) map to Asana completion (marked complete vs open). Tasks are loaded after their parent Project and before any Subtasks.

Cobalt Subtasks map to Asana Subtasks nested under the parent Task. Subtask name, description, assignee, start date, and due date preserve. We resolve the parent Task reference at migration time to maintain the correct nesting depth. Subtasks load after the parent Task has been created in Asana to satisfy the relationship.

Cobalt Milestones map to Asana Milestones within the parent Project. The Cobalt milestone start date and end date determine the Milestone marker date in Asana (typically set to the end date). Milestones load after the parent Project record exists. If the destination Asana workspace uses the Timeline view, the milestone appears as a diamond marker on the Gantt-style layout.

Cobalt project-level custom fields migrate to Asana project-level custom fields with equivalent type mapping: text fields to Asana Text, number fields to Asana Number, date fields to Asana Date, picklist fields to Asana Dropdown with options preserved. We create the custom field in Asana before the project import and attach it to the relevant projects.

Cobalt task-level custom fields migrate to Asana task-level custom fields. Multi-select picklist values in Cobalt map to Asana multi-select fields. We create the field schema in Asana during the schema design phase and populate values during the task import batch. Custom field values on Subtasks attach to the Asana Subtask record.

Cobalt Time Entries have no direct Asana equivalent. Asana does not ship a native time-tracking module; time entries require an integration such as Toggl, Harvest, or TimeCamp, or manual entry. We flag this gap during scoping, preserve the Time Entry data (hours, billable flag, date, user, task reference) in a CSV export for the customer's admin to re-enter in the chosen integration, and do not count it as part of the automated migration scope.

Cobalt Task and Subtask assignees map to Asana Project Members. We extract distinct user references from Cobalt, match them by email against the destination Asana workspace members, and flag any unmatched assignees in a reconciliation queue before migration begins. Asana requires that a Member be added to a Project before they can be assigned to a Task within that Project.

Cobalt file attachments on Tasks and Subtasks migrate as Asana Attachments. We download the source files from Cobalt (coordinating with the customer to provide access), upload them to Asana via the API with the correct task_gid reference, and preserve the original filename and upload timestamp. Attachments load after their parent Task record is confirmed in Asana.

Cobalt comments on Tasks and Subtasks migrate to Asana Task Stories (the chronological activity feed). Comment text, author, and timestamp migrate. We use the Asana Stories API endpoint to post each comment as a story entry on the migrated Task. If Cobalt stores notes separately from comments, Notes migrate as the first story entry on the Task in Asana.

Cobalt tags or labels on Tasks migrate to Asana Tags. Tag names preserve. Asana Tags are workspace-level and can be applied across any project, which matches Cobalt's tag behaviour. We create the tag in the destination Asana workspace during schema setup and apply tag associations during the task import batch.

If the Cobalt account uses a portfolio-level grouping across multiple Projects, we map this to Asana Portfolios (available on Asana Business and Enterprise tiers). Portfolio creation is a post-migration configuration step; we document the portfolio grouping logic during scoping and deliver a written plan for the customer's admin to configure the Portfolio in Asana after the project data has landed.