Migrate from Bluetrait to Salesforce Sales Cloud

Bluetrait Client records map to Salesforce Contact. The Client's associated Company becomes the Contact's AccountId via lookup resolution. We preserve client status (active, inactive, prospect) as a custom picklist field on Contact. Email, phone, address, and custom properties migrate as typed Salesforce fields. The Client's Two-Factor Authentication status does not migrate as it is a Bluetrait-specific security setting.

Bluetrait Company records map to Salesforce Account. The Company name becomes Account Name, the domain becomes Website, and any ABN or registration number becomes a custom field. We create the Account before any Contact import so that the AccountId lookup is satisfied at Contact insert time. If Bluetrait Companies are used as parent entities for multiple Clients, we build the Account hierarchy in Salesforce using the Parent Account field.

Bluetrait Tickets migrate to Salesforce Case if the destination org includes Service Cloud. Ticket status, priority, category, and custom fields map to Case Status, Priority, Origin, and custom Case fields. Ticket history (status transitions, internal notes, assignees) migrates as CaseComments and EmailMessages. We preserve the original ticket created date as Case.CreatedDate via Bulk API timestamp mapping.

If the destination Salesforce org does not include Service Cloud, Bluetrait Tickets migrate as Salesforce Tasks with custom fields carrying ticket-specific properties. In this configuration, the Task WhatId points to the Account (from the mapped Company) and the Task Subject carries the ticket number and title for identification.

Bluetrait Timesheet entries map to a Salesforce custom object (TimesheetEntry__c) or to Tasks linked to the Project or Contact. The mapping type depends on the customer's destination schema: if the Salesforce org uses Field Service Lightning, we map to ServiceAppointment or Project records; otherwise we create a TimesheetEntry__c custom object with fields for Date, Hours, User, and Task link. Timesheet type (billable vs non-billable) migrates as a custom picklist.

Bluetrait Projects link to timesheets, budgets, and tasks. We map project names, budgets, and task counts to a Project__c custom object with lookup to Account and Contact. If the customer's sales process treats projects as billable engagements, we map to Salesforce Opportunity with the project name and a custom budget field. Custom project statuses become Salesforce custom picklist values.

Bluetrait open and historical invoices migrate as Salesforce Quote records or a custom Invoice__c object. Line items, taxes, and payment status transfer as QuoteLineItems or custom InvoiceLine__c records. Closed-Lost or voided invoices migrate with their final status preserved. Recurring billing automation rules do not transfer; we document every recurring rule we encounter and flag it for manual re-configuration in Salesforce or a billing integration (Stripe, Zuora).

Bluetrait Quotes migrate to Salesforce Quote (standard object on Sales Cloud Professional and above). Quote line items map to QuoteLineItem. We preserve the Quote expiry date, approval status, and any attached PDF as a ContentDocument record linked to the Quote. Signed e-signature documents migrate as separate ContentDocument records.

Bluetrait Products map to Salesforce Product2 records. Product code, name, description, quantity, recurring billing frequency, and pricing migrate. Standard Price Book entries are created during import with the active price derived from Bluetrait's product pricing. Recurring billing cadence requires manual re-configuration in Salesforce CPQ or a subscription management tool.

Bluetrait Users map to Salesforce User records by email match. We preserve role, permissions group, and active/inactive status. Two-Factor Authentication status is Bluetrait-specific and does not have a Salesforce equivalent; we note the TFA status in a custom field for the customer's admin to re-configure in Salesforce Identity. Any Bluetrait User without a matching Salesforce User email goes to a reconciliation queue.

Bluetrait Agents are MSP-managed endpoints with watchdog status, installed software, and alert configurations. There is no direct Salesforce equivalent. We map Agent name and basic metadata to Salesforce Asset linked to the Account (representing the managed client's environment). Agent health monitoring, alert thresholds, and watchdog restart configurations do not migrate as they are platform-specific RMM settings. The customer rebuilds monitoring in their chosen RMM tool post-migration.

Bluetrait's CRM module covers Customers, Leads, and their associated activities. We assess the Lifecycle Stage or status property on each CRM record. Prospects without a Company association map to Salesforce Lead. Existing Customers with a Company association map to Salesforce Contact attached to the Account. We preserve the original CRM status as a custom field for audit and reporting.

Bluetrait Knowledge Base articles and their categories can be exported. We map article title, body, and categories to Salesforce Knowledge Article with the appropriate Article Type. Article-to-ticket linking (which articles were referenced in which tickets) is not preserved automatically; we generate a reference document mapping article IDs to ticket IDs for the customer's admin to re-link in Salesforce if Service Cloud is in scope.

Bluetrait Password module entries store credentials for managed systems. These are not accessible via API or CSV export for security reasons. We generate a full inventory of password entry names, associated systems, and folder structure as a reference document for the customer's admin to manually recreate entries in their chosen password manager (1Password, LastPass, Azure Key Vault). This is a post-migration manual step, not a data migration task.