Migrate from Tidy Build to Microsoft Project

Tidy Build Projects map directly to Microsoft Project Plans. We preserve project name, start date, target finish, status (active, on hold, closed), and cost centre metadata as custom fields (Text fields) on the Project record. Tidy Build's project group and budget summary fields migrate to Project-level custom fields for financial reference. The project-level status in Tidy (draft, active, completed) maps to a custom project-level field since Microsoft Project does not have a native project-status property beyond open/closed in the plan.

Tidy Build Tasks and Subtasks map to Microsoft Project Tasks with hierarchical parent-child relationships preserved. Task name, start date, due date, status, and description migrate directly. Tidy Build task assignments (linking tasks to users) map to Assignment records in Microsoft Project with the assigned resource and units loaded. Duration is derived from the start/due date delta if not explicitly stored in Tidy. Milestone-flagged tasks in Tidy become milestone tasks in Microsoft Project.

Tidy Build Time entries linked to Projects and Users map to Microsoft Project Assignment records with hours entered as Work. Each time entry becomes an Assignment against the relevant Task for the relevant Resource. If the destination is Project Online, timephased data can be loaded via the PWA timesheet API. For Project for the web, we store time entry totals as a custom number field on the Assignment record since the Graph API for Project for the web does not natively support timephased assignment data. The original Tidy Build date, duration, and charge-rate references are preserved in custom fields on the Assignment.

Tidy Build Expenses linked to Projects map to Microsoft Project Tasks with expense category and amount stored in custom fields (Text1 for category, Number1 for amount). Each expense record becomes a task record within the parent project so that the expense appears on the project schedule. Expense date and description are stored in additional custom fields (Date1 and Text2). Attachments on Tidy Build expense records are exported as linked files and reattached to the corresponding task in Microsoft Project.

Tidy Build Material Items with pricing levels and location hierarchies map to Microsoft Project Resources of type Material. Each material item becomes a Resource record with the material label, standard cost from the default pricing level, and unit of measure. Material categories map to a custom resource field (Text1) for grouping. Tidy Build's multi-level pricing (pricing tiers per customer or project) is stored as a custom resource field note because Microsoft Project Resources do not support per-instance pricing tiers natively.

Tidy Build Customer records (contact name, company name, billing address) do not have a native Microsoft Project equivalent because Project has no CRM layer. We store the primary customer reference as a custom Text field on the Project record (Text5: customer_name and Text6: customer_contact). If the customer requires full CRM functionality, Microsoft Dynamics 365 Project Operations or a third-party integration is the recommended destination addition. We do not migrate Customer records as a standalone object.

Tidy Build Supplier records similarly have no native Microsoft Project equivalent. We store supplier references as custom Text fields on the Resource record for each material resource linked to that supplier. The supplier contact name and primary supplier identifier are preserved for reference. Full supplier contact records do not migrate as standalone objects.

Tidy Build Quotes have a lifecycle state (draft, sent, approved, lost) and line-item pricing that has no direct Microsoft Project equivalent. We preserve the quote reference number, total amount, and status as custom Text and Number fields on the Project record. Line-item detail is documented in a written quote inventory we deliver to the customer. If the destination is Project Online, the customer may elect to attach the quote PDF to the project as a document via SharePoint.

Tidy Build Purchase Orders with supplier references, line items, quantities, and approval status have no native Microsoft Project equivalent. We map open Purchase Order totals and count to custom fields on the associated Project (Number2: open_po_count, Number3: open_po_value). Full PO line-item detail is documented in a written PO inventory for the customer's admin to handle in their procurement system.

Tidy Build Users map to Microsoft Project Resources. We preserve the Manager vs Team user role designation as a custom resource field (Text3: tidy_user_role) so that the destination system can replicate the access model. Resource type is set to Material for material items and Work for people. The customer's admin provisions the Microsoft 365 accounts that correspond to Tidy Build users as Resources in Project Online or Project for the web before migration begins.

Tidy Build custom field definitions on Projects and Materials are detected via the API schema during pre-migration audit. We map Tidy custom field types (text, number, date, dropdown) to the nearest equivalent Microsoft Project custom field type: text properties map to Text1-30, numeric properties map to Number1-20, date properties map to Date1-10. Custom field values are loaded at migration time against the corresponding Project or Task record. The customer admin creates the destination custom fields in Project Online PWA settings or Project for the web before migration begins.