Migrate from Tidy Build to Asana

Tidy Build Projects map to Asana Projects as the primary container. We preserve project name, status, project group, cost centres, and budget metadata as custom fields on the Asana Project. Tidy Build's cost_centre and budget_total values become numeric custom fields in Asana. Project-level relationships to Quotes, Tasks, Expenses, and Times are preserved by nesting under the same Asana Project.

Tidy Build Tasks and Subtasks migrate to Asana Tasks and Subtasks. Status, assignees, due dates, and description migrate directly. Task Assignments linking a Task to a User become Asana assignee fields. Where Subtasks exist as a separate object in Tidy Build, we nest them under the parent Task in Asana by resolving the parent_id reference at migration time.

Tidy Build Time Entries carry date, duration, charge rate, and optional Task reference. Asana does not have a native per-entry time-tracking object unless the Time Tracking add-on ($10/seat/mo) is enabled. We migrate Time Entries as Task-level custom fields (start time, end time, duration, rate) when the add-on is not in scope, or as native Time Tracking entries when it is. If the customer enables the add-on post-migration, we re-import the historical entries against the correct Tasks.

Tidy Build Expenses link to Projects with amount, category, date, and description. We represent Expenses in Asana as Tasks with a custom Expense Status field (Open, Approved, Rejected), expense category as a single-select custom field, amount as a numeric custom field, and the original Tidy Build expense description in the Task notes. The migrated Task is assigned to the corresponding Asana Project.

Tidy Build Customer records hold contact details, addresses, and billing information. Asana does not have a native CRM-style Account or Contact object. We migrate Customer records as Asana Tags (one per Customer) with the customer's name, primary contact, email, and address stored as Tag fields. Alternatively, Customers can be stored as custom field values on the Projects they relate to, with the customer's name, contact, and billing details as text custom fields.

Tidy Build Supplier records hold vendor contact information and link to Material Items and Purchase Orders. Asana has no native vendor or supplier object. We migrate Suppliers as Asana Tags or as custom field values on Purchase Order Tasks, preserving supplier name, contact email, and address. The customer decides during scoping whether to use Tags or custom fields based on reporting needs.

Tidy Build Material Items carry pricing levels, categories, and location assignments. Asana has no native inventory or material object. We migrate the material hierarchy as structured CSV export with item name, SKU, pricing level, category, and location. For active use, we create Asana custom fields on the relevant Purchase Order Tasks referencing material values. The CSV export is delivered alongside the migration as a supplemental data file.

Tidy Build Quotes have their own lifecycle state (draft, sent, approved, lost) and contain line items with pricing. Asana has no native Quote object. We migrate Quote metadata (customer, project, total value, status, date) as custom fields on an Asana Task with a Quote Status enum custom field. Quote line items are included in the CSV export delivered alongside the migration. The customer's admin links the CSV to the relevant Asana Project or attaches it to the Quote Task.

Tidy Build Purchase Orders contain supplier references, line items, quantities, and approval status with open/closed state. We migrate PO metadata as custom fields on an Asana Task with a PO Status enum custom field. Supplier reference is resolved to the corresponding Supplier Tag. Line items and quantities are included in the CSV export. The customer decides whether to use separate Asana Projects per PO or aggregate POs under a single procurement Project.

Tidy Build User accounts include name, email, role, and time profile. Manager versus Team user roles from Tidy Build are preserved as a custom field on the Asana User record (tidy_user_role__c). We match Users by email. Any Tidy Build User without a matching Asana User account goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Tidy Build supports custom fields on Projects. We detect custom field definitions via the Tidy Build API schema, map each to the equivalent Asana custom field type (text, number, date, single-select enum), and apply the values to the migrated Project records. Custom field definitions are created in the Asana workspace before the migration phase begins.

Tidy Build supports custom fields on Material Items. We migrate these as columns in the Material Items CSV export. If the customer requests active material lookup from within Asana Tasks, we create custom fields on the relevant Purchase Order Tasks and populate them from the material data.