Migrate from Tidy Build to Jira

Tidy Build Projects map to Jira Projects as the top-level container. We preserve the project name, status (Active, On Hold, Closed), project group assignment, cost centres, and budget metadata as Jira Project fields or custom fields on a configuration issue within the project. Jira Project key prefixes are assigned during schema setup, and the Tidy Build project identifier is preserved in a custom Jira field for traceability.

Tidy Build Quotes have no native Jira equivalent. We create a custom Issue Type named Quote in the target Jira project with a custom status field replicating Quote lifecycle states (Draft, Sent, Approved, Lost). The quote total, line items, and pricing tier migrate as Jira fields. If Jira Service Management is present, Service Desk request types can also serve as the Quote container. The mapping is 1:1 with lifecycle state preserved as a custom field rather than a native Jira workflow status.

Tidy Build Customers migrate to Jira as Accounts (if Jira Software Premium with Assets is present) or as Jira user accounts with a Customer designation. Address, contact details, and billing information transfer to custom fields on the Jira user record or to a dedicated Customer Issue Type. Customer-specific material pricing tiers from Tidy Build become custom fields on the migrated record.

Tidy Build Suppliers have no native Jira type. We map them to Jira user accounts with a Supplier designation or to a Contact Issue Type depending on the Jira edition. Supplier contact information, lead times, and procurement notes migrate as custom fields. The link between a Supplier and their associated Material Items is preserved via Jira issue links or a custom lookup field on the Product record.

Tidy Build Material Items map to Jira Products with a flat material hierarchy. Subcategories and multi-level pricing structures are flattened to a single product hierarchy level per Jira's catalogue model. Material cost, pricing levels (retail, trade, wholesale), and location assignments transfer to Jira custom fields on the Product. Jira Product Catalogue is available on Software Premium and above; on lower tiers we map Materials to Issues with a Material Type designation and preserve the hierarchy in a custom parent-link field.

Tidy Build Tasks and Subtasks map directly to Jira Issue (type Task) and Jira Issue (type Subtask) respectively. Status, assignee (via User mapping), due date, description, and any Tidy Build Task Assignments migrate. Where Subtasks exist as a separate API object in Tidy Build, we maintain the parent-child relationship via Jira's issue-link or parent-link field. Jira Subtask must be enabled on the target project before this mapping runs.

Tidy Build Time Entries map to Jira Worklog records attached to the target Issue. Date, duration, billable/non-billable flag, and charge rate transfer as Worklog fields. The Tidy Build time profile (hourly rate) is preserved in a custom Issue field or the Jira User's time-tracking configuration. Jira time-tracking must be enabled on the target project. If the destination Jira edition does not include time-tracking, Times migrate as Task records with date and duration fields.

Tidy Build Expenses linked to Projects map to Jira Issues of a custom Expense type. Amount, category (expense type), date, description, and approval status transfer as Jira fields. Attachments on Tidy Build expenses export as Jira attachments and re-attach to the corresponding Expense issue. The link to the originating Project is preserved via Jira project context or a custom Project lookup field on the Expense issue.

Tidy Build Purchase Orders have no native Jira equivalent. We create a custom Issue Type named Purchase Order with custom fields for supplier reference, line items (as a text or table field), quantities, and approval status. The open/closed PO status from Tidy Build maps to Jira Issue status (Open/Done). Supplier linkage is resolved via the Supplier mapping. PO PDFs and attachments migrate as Jira attachments to the PO issue.

Tidy Build Sales Records aggregate invoiced work against a Project. We map these to Jira Issues (type Task or Story depending on the customer's Jira project convention) with custom fields carrying the sales amount, line items, and associated project reference. The link to the originating Tidy Build Project is preserved in a Jira custom field for reporting against the original project structure.

Tidy Build Users map to Jira user accounts resolved by email address. The Manager vs Team role designation from Tidy Build is preserved as a custom Jira user property (e.g. tidy_role__c) so the destination Jira admin can replicate the access model using Jira's group membership and project roles. Any Tidy Build User without a matching Jira account is held in a reconciliation queue for the admin to provision before record migration resumes.

Tidy Build custom fields on Projects and Materials are detected via the API schema at scoping and pre-created in the target Jira project as typed custom fields before any data import begins. Field types (text, number, date, picklist) are mapped to equivalent Jira field types. Tidy-specific picklist options are pre-loaded as Jira custom field options. Validation rules and required-field enforcement are temporarily relaxed during migration load and reinstated after validation sign-off.