Migrate from Projectworks to Asana

Projectworks Projects map to Asana Projects with project name, description, status, start date, and end date preserved. Custom fields on the Project level (such as Client Name, Project Type, or Cost Center) map to Asana custom fields with type-matching: single-select options map to Asana enum fields, text fields map to text, and date fields map to date. Milestones nested under the Project carry their own due dates and completion status and are migrated after the parent Project exists so dependency resolution is satisfied.

Projectworks Tasks map to Asana Tasks with title, description, assignee (resolved to Asana User by email), due date, and start date preserved. Subtasks under Projectworks Tasks map to Asana Subtasks within the task hierarchy. Custom fields on Tasks (such as Task Category, Priority, or Department) map to Asana task-level custom fields with type matching. Asana's Task API does not support a native billable/non-billable flag, so that value is stored in a custom field if required by the customer.

Projectworks Milestones map to Asana Milestones. We preserve milestone name, due date, and completion status linked to their parent Project. Asana Milestones are a project-level sub-object and must be created after the parent Project is confirmed to exist in the destination. If the customer used milestones as a project financial checkpoint (e.g., invoicing milestone), that financial context is flagged as a non-migratable note since Asana has no billing module.

Projectworks Time Entries map to Asana Tasks created under the relevant Project with the hours value stored in a custom duration field and the entry date preserved. Note that Projectworks timesheets capture duration only, not start and finish times. We flag this gap during discovery and confirm whether duration-only timesheets meet billing requirements in Asana. For firms using third-party time-tracking tools (Toggl, Harvest, Timely) post-migration, we document the time entry mapping so integrations can be configured to re-associate migrated hours with live tracking.

Projectworks People records map to Asana Users with name, email, and role preserved. Billable hourly rates stored on the Projectworks People record do not have a native Asana field and are flagged for extraction to a separate CSV for re-import into a third-party time-tracking or billing tool. Capacity, utilization, and leave management data from Projectworks People records have no Asana equivalent; we document these fields for the customer's admin to handle separately in a resource management tool or HR system.

Projectworks Company records map to Asana Organizations. Company name, address, billing details, and any custom fields applied to the Company object migrate. Asana's Organization object is a workspace-level entity used for grouping People, so we use the Company domain or name as the Organization identifier. If the customer used Companies as a project billing entity, that context is flagged since Asana has no native invoicing capability.

Projectworks Contact records map to Asana People within the relevant Organization. Contact name, email, phone, and any custom fields migrate. The relationship to the parent Company from Projectworks maps to membership within the corresponding Asana Organization. Asana People do not support custom fields at the person level in the same way Projectworks Contacts do; we map supported custom field types and flag any that cannot be transferred.

Projectworks custom fields on Projects, Tasks, People, Companies, and Contacts map to Asana custom fields of the corresponding type. Single-select options in Projectworks map to Asana enum fields; text fields map to text; number fields map to number; date fields map to date. Dropdown and multi-select field values require a pre-migration enumeration review because Asana enum fields must be created with their options before task import. Custom field schema varies per firm; we enumerate all custom fields during discovery and produce a type-matched mapping table before any data moves.

Projectworks Invoices (with fixed-fee and hourly rate line items) cannot migrate to Asana because Asana has no invoice generation or financial document object. We extract invoice headers, line items, amounts, and status to a CSV for re-import into the customer's chosen accounting platform (typically Xero, QuickBooks, or DEAR Systems). We flag any Xero sync settings configured in Projectworks so that the customer's finance team can re-establish the Xero connection in the accounting tool without duplicate invoice pushes.

Projectworks Expenses (reimbursable and non-reimbursable) cannot migrate to Asana because Asana has no expense tracking module. We extract expense records with category, amount, reimbursement status, linked Project, and linked Person to a CSV for re-import into the customer's accounting tool. If Projectworks is connected to Xero for expense export, we flag the Xero connection credentials and sync rules for re-establishment in the destination accounting system.

Projectworks Budgets (planned vs. actual revenue and cost tracking per project) cannot migrate to Asana because Asana has no financial budget or burn-rate object. We extract budget line items with planned amounts, actuals, and variance data to a CSV for the customer's finance team to re-import into a reporting or budgeting tool. Budget data is purely financial and is outside Asana's work management scope.

Projectworks Quotes with custom fields and line items are extracted to a CSV for re-import into the customer's CRM or accounting system. Asana does not have a quote or proposal object. We enumerate all quote fields during discovery and flag any custom field schema that requires mapping in the destination system.