Migrate from Bluetrait to Microsoft Dynamics 365 Sales

Bluetrait Company records map directly to Microsoft Dynamics 365 Sales Account. The Company name becomes Account Name; address fields map to Address composite fields in Dataverse. We use Company unique ID as an external key for deduplication during import. Account is created before any Contact import so that the CustomerId lookup on Contact is satisfied at insert time. If the destination org uses Business Units, we map the Bluetrait organisation to a specific Business Unit during schema setup.

Bluetrait Client records map to Microsoft Dynamics 365 Sales Contact. Client first name, last name, email, phone, and address map to Contact firstname, lastname, emailaddress1, telephone1, and address fields. The link between Client and Company in Bluetrait becomes the Contact.parentcustomerid lookup pointing to the Account record created from the paired Company. We resolve the parent lookup at migration time by matching Client.company_id to the imported Account's external key.

Bluetrait Tickets map to Dynamics 365 Case (incident) records. Ticket subject becomes Case title, description becomes Case description, status maps to Case status (Active/Resolved/Closed), priority maps to Case priority, and the due date maps to Case/ServiceTask due date. If Microsoft Dynamics 365 Sales does not have Service Cloud enabled, we map tickets to a custom Case entity on the target Dataverse environment and flag this as a pre-migration configuration requirement. Ticket custom fields and tags migrate as custom fields on Case.

Ticket status change history in Bluetrait (Opened, In Progress, Waiting, Resolved, Closed) maps to Case annotations or a custom CaseStatusHistory table in Dynamics 365 because the standard Case entity stores the current status but not the full transition log. We create annotation records for each status transition with a timestamp and the Bluetrait status value preserved as text.

Bluetrait Timesheet entries (date, hours, user, task/project link, timesheet type) map to Dynamics 365 Note records attached to the relevant Contact or Account, or to a custom TimesheetActivity entity if the destination org supports custom activities. We include the date, hours, billable flag, and project reference in the Note body as structured text. The timesheet type (billable/non-billable) is preserved in a custom field. Bluetrait's auto-import of timesheet items onto invoices does not migrate; we document the mapping for manual rebuild in Dynamics 365 if the customer has Finance or Sales modules.

Bluetrait Projects with budgets and task counts map to Dynamics 365 Opportunity (if the project is sales-driven) or to a custom Project entity if the destination uses Project Service Automation. Project name, budget amount, and task count migrate as Opportunity.name, estimated value, and a custom task_count__c field. Custom project statuses and budget thresholds migrate as custom fields. We confirm the correct destination object with the customer during scoping because the mapping depends on whether Projects represent billable sales work or internal delivery work.

Bluetrait invoices and quotes map to Microsoft Dynamics 365 Sales Invoice or Quote records. Line items, taxes, and payment status migrate as InvoiceDetail lines. Open and historical invoices transfer as static records; the invoice total, tax amount, and payment status are preserved. Recurring billing automation rules (auto-billing from timesheets) do not export via API or CSV and are documented for manual rebuild in Dynamics 365's repeating invoice or Power Automate flow equivalents.

Bluetrait Products with quantities, recurring billing frequencies, and pricing map to Dynamics 365 Product2 records. Product name, SKU (product code), and standard price migrate. Recurring billing frequency maps as a custom field or product property; the cadence requires manual re-setup in Dynamics 365 if the customer uses subscription-based billing.

Bluetrait Agent records (MSP edition) represent managed endpoints with watchdog status, installed software, and alert configurations. We map agent name, associated Company, and endpoint metadata to a custom Endpoint or Device entity in Dynamics 365 Dataverse. Agent health monitoring and alert automation do not migrate because RMM health dashboards are not Microsoft Dynamics 365 Sales objects; these are documented for rebuild in Microsoft Intune or a dedicated RMM tool.

Bluetrait Users (username, role, permissions group, Two-Factor Authentication status) map to Dynamics 365 User records by email match. Active/Inactive status migrates. Bluetrait passwords do not export for security reasons and must be reset post-migration. Users without a matching Dynamics 365 tenant email go to a reconciliation queue for the customer admin to provision.