Migrate from Tidy Build to Trello

Tidy Build Projects map to Trello Boards. Project name becomes the Board title, and Project status (active, on-hold, completed) maps to a Board label or a List named by status. Tidy Build cost-centre metadata and budget fields migrate as typed Card custom fields on a template Card in each Board so the financial context is preserved and accessible to anyone opening the Board.

Tidy Build Tasks map to Trello Cards. Task name becomes the Card title, description migrates as the Card description, due date migrates as the Card due date, and assignee (User) migrates as a Card member. Subtasks in Tidy Build become Checklist items on the parent Card. Task status maps to the Card's List position (To Do, In Progress, Done) using a configurable status-to-list rule defined at scoping.

Tidy Build Customers are contact records with address and billing information. Since Trello has no native contact or CRM object, Customers can be modelled as Board members (for client-facing project Boards) or stored as a structured Members list in a companion Board. Customer-specific material pricing tiers migrate as a custom field on the relevant Project Board. The customer selects the strategy during scoping based on whether they use Trello for client collaboration or internal project tracking.

Tidy Build Suppliers hold vendor contact information and are linked to Material Items and Purchase Orders. Trello has no native supplier object. We create a dedicated Suppliers Board in the Trello Workspace with one Card per Supplier, containing contact details, lead times, and linked material information. Purchase Orders reference the Supplier Card via a custom field.

Tidy Build Material Items carry pricing levels, categories, and location assignments. Trello has no native inventory or material object. We migrate material data as a structured companion sheet (CSV attached to the Project Board) or as typed custom fields on a Project Board Card if the customer requires material data accessible within Trello directly. Multi-level pricing structures flatten to a single custom field or Notes section due to Trello's limited custom field types.

Tidy Build Quotes are distinct objects with draft/sent/approved/lost lifecycle states and line items. Trello has no native Quote object. We model each Quote as a Card on a dedicated Quotes Board with a lifecycle custom field (Draft, Sent, Approved, Lost) and line items stored in the Card description or as a Checklist. The customer should treat Quote migration as a data-preservation exercise rather than a functional replacement; Trello does not support quote-generation workflows natively.

Tidy Build Purchase Orders contain supplier references, line items, quantities, and approval status. We model Purchase Orders as Cards on a dedicated Orders Board with a status custom field (Open, Approved, Received, Closed), supplier reference (linked to the Supplier Card in the companion Suppliers Board), and line items in the Card description. PO approval workflows cannot migrate because Trello has no native approval routing.

Tidy Build Time Entries link to Projects, Users, and optionally Tasks with date, duration, and charge-rate. Trello has no native time-tracking object. We migrate time-entry data as a companion CSV file attached to the Project Board, or as typed custom fields on individual Cards if the time-entry count is small and the customer wants per-task time visible within Trello. Butler-based time-tracking Power-Ups are available on Trello's Premium plan but require separate configuration post-migration.

Tidy Build Expenses link to Projects and are categorised by Expense Type with amount, date, and description. We migrate expense data as typed custom fields on the Project Board Card (amount, category, date) or as a structured companion CSV. Expense attachments migrate as Card attachments. Trello's Standard or Premium plan is required for custom fields beyond the free-plan limit of one per Board.

Tidy Build Users with Manager vs Team role designations map to Trello Workspace Members. The Manager/Team designation migrates as a custom property on the Trello member profile. We resolve Users by email match. If a Tidy Build User has no corresponding Trello account, the account is provisioned by the customer before migration proceeds.

Tidy Build Custom Fields on Projects and Materials migrate to Trello Card custom fields. Trello supports text, number, date, dropdown, checkbox, and rating custom field types. We detect the Tidy Build custom field type via the API schema and map to the closest Trello custom field type. Boolean fields map to Trello checkbox custom fields; text fields map to text custom fields; date fields map to date custom fields.

Tidy Build Sales Records aggregate invoiced work against a Project with amounts and line items. Trello has no native Sales object. We migrate Sales Record data as Card description text or a structured companion CSV attached to the Project Board, preserving invoice amounts, dates, and line-item summaries for financial reference.