Migrate from Bluetrait to Zoho CRM

Bluetrait's CRM module stores Customers and Leads in one object with a lifecycle status field. We split these at migration time using Bluetrait's lifecycle stage property: prospects with no associated ticket or billing history map to Zoho CRM Lead, and active customers with timesheet or ticket history map to Zoho CRM Contact. The original Bluetrait lifecycle stage is preserved in a custom field for audit and segmentation after migration.

Bluetrait Company records map to Zoho CRM Account. The company domain becomes the Account Website field. If the Bluetrait account uses the Client object as a sub-record of Company, we map Client fields (phone, address, primary contact flag) to Zoho Contact fields linked via the Account lookup. We create the Account first so that the Account-Contact relationship is satisfied at insert time.

Bluetrait Tickets migrate to Zoho CRM Cases if the destination uses Zoho Desk or Service Cloud. Ticket status, priority, due date, assignee, custom fields, and internal notes transfer directly. Ticket conversation history (customer replies and agent responses) migrates as Zoho CRM Notes or as EmailMessage records linked to the Case. If the destination does not include a service desk module, tickets migrate as Tasks in the CRM module with ticket ID preserved as a custom field for cross-reference.

Bluetrait timesheet entries (date, hours, user, project link, task link) map to Zoho CRM Activities. Each timesheet type can be included or excluded from invoice descriptions during import. We preserve the project link as a custom lookup field on the Activity so that timesheet-to-project associations are not lost. Billable versus non-billable flags map to a custom Zoho Activity field.

Bluetrait Projects (with budget, task count, and status) map to Zoho CRM Deals if the project is sales-related, or to a Zoho custom module called Projects if the customer's use case requires project management features. Project budgets and task counts migrate as custom fields. Custom project statuses map to Zoho picklist values we configure before migration.

Open and historical invoices, quotes, and purchase orders transfer as static records with line items, taxes, and payment status preserved. Recurring billing automation rules are not exposed via API or CSV and do not migrate; we document every recurring configuration found in the source account as a reference for the customer to reconfigure in Zoho Books or Zoho CRM. We flag any auto-billing-from-timesheets configuration as a manual post-migration setup item.

Bluetrait Products (with quantities, recurring billing frequencies, and pricing) map to Zoho CRM Products. Product-to-billing associations transfer as custom line-item properties. Recurring billing frequency requires manual reconfiguration in Zoho CRM or Zoho Books because the frequency field types differ between platforms.

Bluetrait Agents represent managed endpoints with watchdog status, installed software, and alert configurations unique to Bluetrait's RMM layer. This data has no equivalent in Zoho CRM and does not migrate. We provide a summary count of active agents and the software list for the customer to use in their endpoint management documentation. Endpoint health monitoring and alerting must be re-established in the customer's chosen RMM tool.

Bluetrait Users (username, role, permissions group, Two-Factor Authentication status) map to Zoho CRM Users. We match by email address. Any Bluetrait User without a matching Zoho CRM User is placed in a reconciliation queue for the customer's admin to provision. Passwords do not migrate for security reasons; users must complete a password reset post-migration.

Bluetrait custom CRM fields (property types: text, number, date, checkbox, dropdown, multi-select) map to Zoho CRM custom fields with corresponding types. Multi-checkbox fields from Bluetrait map to Zoho multi-select picklists. We pre-create the custom field schema in the Zoho destination before migration begins. Custom field API names are preserved with a _c suffix per Zoho convention.

Bluetrait knowledge-base articles and their categories can be exported. We map articles to a Zoho custom module called Articles with Title, Body (rich text), Category, and Tags fields. Article-to-ticket linking is not preserved automatically; we document these associations as a reference CSV for manual re-linking in Zoho Desk or the CRM knowledge base.

Bluetrait's Passwords module stores credentials for managed systems. For security reasons, passwords are not accessible via API or CSV export. We cannot migrate password entries. We generate a full inventory of password entries (names, associated systems, folder structure) as a reference CSV so the customer can manually recreate entries in their destination password manager (Zoho Vault, 1Password, Bitwarden, or equivalent).