Migrate from PROAD to Asana

PROAD Projects map directly to Asana Projects. Project name, description, status, start date, and end date migrate 1:1. We preserve the project status (active, completed, on hold) as an Asana project custom field since Asana's native project states are limited to public and private visibility. Milestone dates within the project carry over as Asana milestones on the Advanced and Enterprise plans; on Starter plans they are stored as due-date tasks flagged with a milestone tag.

PROAD Subprojects map to Asana Projects when they represent independently tracked workstreams, or to Sections within the parent Asana Project when they represent phase groupings. We determine the split during scoping based on whether the Subproject has its own assignees, deadlines, and deliverables distinct from the parent Project. Subproject task hierarchies nest under the parent project's task list, preserving the original relationship.

PROAD's combined Client records contain company details and a primary contact in one object. We split these into Asana Companies (containing the organization name, address, and domain) and Asana Contacts (containing the individual name, email, phone, and role). The primary client contact in PROAD becomes the primary Contact linked to the Company. Any secondary contacts in PROAD migrate as additional Contact records under the same Company.

PROAD Contact records (standalone contact entries not linked to a Client) migrate to Asana Contacts with name, email, phone, and address fields preserved. Custom fields on PROAD Contacts map to Asana custom fields on the Contact record. We match Contacts to their parent Company using the linked Client relationship computed during the Client split phase.

PROAD Tasks map directly to Asana Tasks with task name, description (as Notes), due date, priority, and assignee assignments preserved. Subtask relationships migrate as nested Asana Tasks under their parent Task. On Asana Starter plans, subtasks are independent tasks linked by a custom field reference; on Advanced and Enterprise, subtasks are native nested sub-tasks. We flag this distinction during scoping so the customer knows whether their plan supports native subtask nesting.

PROAD Milestones (date-based markers within a project timeline) map to Asana Milestones on Advanced and Enterprise plans. Milestone name, target date, and associated project link carry over. Milestone completion status is stored in a custom field migratedate_completed__c because Asana Milestones do not natively track completion state separate from the associated task.

PROAD Time Entries (hours logged against a task or project, attributed to a user, with billable flag and rate) migrate to Asana time tracking entries. The billable flag from PROAD migrates to a custom field migratedate_billable__c on the time entry because Asana's time-tracking module does not natively distinguish billable from non-billable hours on the entry itself. Hourly rate information from PROAD migrates to a custom field migratedate_rate__c if the source data includes per-user or per-project rate settings.

PROAD Tickets (issue requests linked to clients or projects) migrate to Asana Tasks with ticket name, description, status, priority, and conversation history preserved. Conversation history migrates as task comments in Asana. The original client or project linkage is stored in a custom field migratedate_parent_link__c to preserve the association that would otherwise be lost since Asana Tasks do not natively support a client or project parent object outside of the task's assignee and project membership.

PROAD custom fields on Projects, Tasks, and Contacts map to Asana custom fields of equivalent type (text, number, date, dropdown). Dropdown field options in PROAD migrate to Asana enum values. We inventory all custom fields during discovery, pre-create them in the destination Asana workspace, and flag any PROAD custom field type with no direct Asana equivalent (for example, PROAD's formula fields) as requiring a custom field type decision during scoping.

PROAD User accounts map to Asana workspace members by email address. We extract every distinct user referenced on Projects, Tasks, Subprojects, and Time Entries and match against the Asana destination workspace. Inactive or suspended PROAD accounts are flagged and excluded from migration unless the customer explicitly requests they be provisioned in Asana.

File attachments on PROAD Tasks and Projects migrate to Asana as task attachments linked via Asana's attachment API. We flag any attachment exceeding Asana's 100MB file size limit during discovery and handle these as a separate download-and-rehost pass. Attachments linked to Tickets migrate as attachments on the corresponding Asana Task.

Tags applied to PROAD Projects, Tasks, and Contacts normalize to Asana Tags. We deduplicate tag names introduced by inconsistent casing in the source data during the transform phase before import.