Migrate your Tidy Build data

Projects are the primary data container in Tidy Build. We migrate them with their status, project group, cost centres, and associated metadata. Relationships to Quotes, Tasks, Expenses, and Times are preserved via ID mapping at migration time.

Quotes are a distinct object with their own lifecycle state (draft, sent, approved, lost). We migrate the full quote record including line items, pricing, and lifecycle status. Destination systems may require quote-to-deal conversion mapping.

Customer records include contact details, addresses, and billing information. We migrate them as standard contact/account objects and preserve any customer-specific material pricing tiers as custom fields.

Supplier records hold vendor contact information and are used within material procurement and purchase order workflows. We migrate Suppliers and link them to their associated Material Items and Purchase Orders.

Material Items carry pricing levels, categories, and location assignments. We preserve the full material hierarchy including subcategories and multi-level pricing structures. Material cost history is mapped as a custom field if the destination lacks a native cost-history model.

Tasks and their Subtasks are migrated with status, assignees, and due dates. Task Assignments linking Tasks to Users are preserved. Where Subtasks exist as a separate object in Tidy Build, we maintain the parent-child relationship.

Time entries are linked to Projects, Users, and optionally Tasks. We migrate Times with date, duration, and charge-rate references. Where the destination uses a different time-tracking schema (e.g. billing-only vs. time-and-materials), we apply a mapping step.

Expenses are linked to Projects and categorised by Expense Type. We migrate the expense record with amount, category, date, and description. Attachments on expenses are exported as linked files and reattached at the destination.

Purchase Orders contain supplier references, line items, quantities, and approval status. We preserve the PO record and its relationship to the associated Supplier. Open/closed status is migrated as a field.

Sales records aggregate invoiced work against a Project. We migrate the Sales record with amounts and line items. The destination CRM may not have a native Sales object, in which case we map Sales to Opportunities or Invoice records.

User accounts include name, email, role, and time profile. Manager vs Team user roles are preserved as a custom property since not all destination systems model these Tidy-specific role tiers.

Tidy Build supports custom fields on Projects and Materials. We detect custom field definitions via the API schema and apply field-level mapping at migration time. Custom field types (text, number, date, dropdown) are matched to equivalent destination field types where available.