Migrate from Tidy Build to monday Work Management

Tidy Build Projects map to monday.com Boards. Project status, project group, cost centres, and budget metadata migrate into custom columns on the Board. We use the monday.com Boards API to create the Board with the correct workspace and subscribe the relevant Team Members. Sub-projects and phases within a Tidy Build Project map to Groups within the Board. The Board description carries the original Tidy Build cost-centre identifier for traceability.

Tidy Build Quotes migrate as Items on a dedicated Quotes Board. Quote lifecycle state (draft, sent, approved, lost) maps to a Status column with labels matched to the original Tidy Build state values. Line items migrate as sub-items with product name, quantity, unit, and price columns. Quote total and tax calculations migrate to number columns. We preserve the Quote's linked Project as a Board Relation column pointing back to the Project Board.

Tidy Build Customers migrate as Items on a Contacts Board. Contact name, phone, email, and billing address fields map to typed monday.com columns. Customer-specific material pricing tiers from Tidy Build migrate as custom number columns on the Item. If the customer uses monday.com's native Contacts integration, we map to that instead and preserve the pricing tier data as a custom field.

Tidy Build Suppliers migrate as Items on a Suppliers Board. Supplier contact name, company, phone, and email map to typed columns. Supplier notes and payment terms migrate as text columns. We preserve the link between Supplier Items and associated Material Items via a Connect Column so that procurement relationships are visible in monday.com without a custom integration.

Tidy Build Material Items migrate as Items on a Materials Board. Material name, category, unit, and location hierarchy migrate to columns. Multi-level pricing tiers (e.g. Level 1, Level 2, Level 3) migrate as separate number columns named by tier. Cost history migrates as a text column with date-stamped entries if the destination needs audit traceability. Material Supplier links use a Connect Column pointing to the Supplier Board Item.

Tidy Build Tasks map to Items on the Project Board (or a dedicated Tasks Board linked by a Board Relation column). Subtasks map to Sub-items attached to the parent Item. Task status, assignees, and due dates migrate to Status, Person, and Date columns respectively. Task Assignments linking Tasks to Tidy Build Users preserve as Person column assignments on the monday.com Item. Subtask structure is maintained as sub-item nesting so that task hierarchies are preserved in the destination.

Tidy Build Time Entries link to Projects, Users, and optionally Tasks. We migrate each Time Entry as an Item on a Time Tracking Board with date, duration (as a number column in hours or minutes), and charge-rate columns. A Board Relation column links the Time Entry Item to the parent Project Board Item. Assignee maps to a Person column. If the destination monday.com plan includes the native Time Tracking column, we use that; otherwise we use custom number columns for duration and rate.

Tidy Build Expenses migrate as Items on an Expenses Board. Expense amount, category (Expense Type), date, and description migrate to typed columns. A Board Relation column links to the parent Project Board Item. Receipt or attachment files from Tidy Build migrate as file uploads attached to the monday.com Item via the Files API. Open/closed status from Tidy Build maps to a Status column with labels matched to the original values.

Tidy Build Purchase Orders migrate as Items on a Purchase Orders Board. Supplier reference, line items (as sub-items), quantities, and approval status migrate to typed columns. Approval status maps to a Status column with labels (e.g. pending, approved, rejected). A Connect Column links the PO Item to the associated Supplier Item on the Suppliers Board. PO open/closed status migrates as a Status column label set.

Tidy Build Users migrate as monday.com Workspace members invited to the relevant boards. The Tidy Manager versus Team user role designation is preserved as a custom text column on a User Info Board or as a tag on each user's profile. monday.com does not have a native Manager/Team role distinction, so the access model is reconstructed using monday.com Workspace permissions (full member, viewer) and board-level permission tiers. The customer's admin sets these post-migration.

Tidy Build Sales records aggregate invoiced work against a Project. We migrate Sales as Items on a Sales Board with amount, line items (as sub-items), and date columns. A Board Relation column links each Sales Item to the associated Project Board Item. If monday.com's CRM product is in use, Sales records can alternatively map to Deal items with custom columns carrying the construction-specific billing data.

Tidy Build custom fields on Projects and Materials are detected via the API schema during scoping. Each custom field maps to a typed monday.com column: text fields to Text Column, number fields to Number Column, date fields to Date Column, and dropdown fields to Status Column with the values set as labels. Custom field type constraints (e.g. minimum/maximum values) are noted in the migration inventory for the customer to configure post-migration in monday.com's column settings.