Migrate from Bluetrait to HighLevel

Bluetrait Tickets map to GoHighLevel Opportunities if the destination uses the sales pipeline model, or to Cases if Service Cloud is active. We preserve ticket subject as Opportunity name or Case subject, ticket status as pipeline stage or case status, due dates as custom date fields, and internal notes as Opportunity notes or Case description. Tags from Bluetrait migrate to GoHighLevel custom multi-select fields or Opportunity tags. Custom fields on Bluetrait tickets require pre-creation in GoHighLevel before migration so that the field IDs are available for mapping.

Bluetrait Companies map directly to GoHighLevel Companies. The Company name, address, phone, website, and custom fields transfer. We use Company name as the dedupe key during import. If the destination GoHighLevel account uses Contacts linked to Companies rather than a flat Contact model, we create Company records first so that the lookup relationship is satisfied on Contact insert. Australian GST details stored as custom fields in Bluetrait transfer to GoHighLevel custom fields on the Company record.

Bluetrait Clients map to GoHighLevel Contacts. Client name, email, phone, address, and custom CRM fields transfer. The client-to-company association in Bluetrait maps to the Contact-to-Company relationship in GoHighLevel. If Bluetrait stored multiple contacts per client as separate Client records, we preserve each as a distinct GoHighLevel Contact with the same Company link. 2FA status from Bluetrait cannot be transferred and requires manual re-enrollment in GoHighLevel.

Bluetrait Timesheet entries map to GoHighLevel Tasks. Each entry's date, hours, user, task/project link, and timesheet type transfer. The timesheet type can be stored as a custom field in GoHighLevel rather than as the Task subject, preserving the original description. We link tasks to the relevant Contact (the client the timesheet was for) and Company using the WhatId relationship. Bluetrait timesheet entries that were auto-imported to invoices are flagged in our migration report for the customer to reconcile against the billing inventory.

Bluetrait Projects map to GoHighLevel Opportunities with project name as the Opportunity name, budget as a custom currency field, and task count as a custom number field. Project status becomes a GoHighLevel custom picklist. If the customer uses project tracking as a revenue model (milestone billing), we recommend creating Opportunities with stages representing milestones rather than a separate custom object, since GoHighLevel's custom object support requires the SaaS Pro plan or above.

Bluetrait Invoices and Quotes migrate as Opportunity records with line items represented as Opportunity product entries or custom line-item fields. Open and historical invoices transfer with line items, taxes, and payment status preserved as custom fields. Recurring billing automation does not migrate; we document every recurring billing configuration encountered (frequency, auto-billing rule, linked timesheet type) and provide it as a manual setup guide for GoHighLevel or a Zapier-to-accounting-software integration plan. Payment status becomes a custom picklist field on the Opportunity.

Bluetrait Products (with quantities, recurring billing frequencies, and pricing) map to GoHighLevel Products. Product-to-billing associations transfer as Opportunity line items linked to the GoHighLevel Product. Recurring billing frequency stored in Bluetrait becomes a custom field on the GoHighLevel Product record since GoHighLevel's native product model does not carry subscription cadence as a standard field. Manual product re-setup in GoHighLevel's product catalog is recommended post-migration for any subscription-based items.

Bluetrait Agent records (endpoint health, watchdog status, installed software, alert configurations) are MSP-specific and have no GoHighLevel equivalent. We extract agent endpoint names, software lists, and alert configurations as a structured CSV inventory and provide this as a reference document for the customer to re-enter into their chosen RMM tool (GoHighLevel has no native RMM; customers typically pair with NinjaOne, Syncro, or Auvik post-migration). Agent health monitoring and watchdog restart rules cannot be automated in GoHighLevel.

Bluetrait Users (username, role, permissions group) map to GoHighLevel Users. We match by email address. Permissions groups from Bluetrait require manual translation to GoHighLevel team roles and access permissions because the permission models differ structurally. Any Bluetrait User without a matching GoHighLevel User goes to a reconciliation queue for manual provisioning. Passwords are not exported from Bluetrait for security reasons; all migrated users must reset their GoHighLevel password post-migration.

Bluetrait Knowledge Base Articles export as content but article-to-ticket linking does not preserve automatically. We extract article content, categories, and any manually documented ticket associations. In GoHighLevel, articles can be stored as Opportunities notes, external documents, or rebuilt in GoHighLevel's Sites module. We document the source associations for the customer to re-link manually in the destination.