Migrate from Bluetrait to Freshsales

Bluetrait Companies map to Freshsales Accounts. The Company name becomes the Account name, domain and contact email become website and email fields. Companies are created before Clients in migration order because Freshsales Accounts are the parent of Contacts. If the source account has Company-level custom fields, we pre-create matching custom fields in Freshsales before import so the Account mapping is complete.

Bluetrait Clients map to Freshsales Contacts. The Client's associated Company resolves to a Freshsales AccountId reference at migration time. If the source Client represents an unqualified prospect (not yet a formal account), it maps to a Freshsales Lead instead; we determine this from the Client's lifecycle or status field during scoping and present the routing logic as part of the object mapping matrix before migration begins.

Bluetrait Tickets do not have a single Freshsales equivalent because Freshsales distinguishes pipeline opportunities (Deal) from support issues (Case). We classify Tickets during scoping: sales-cycle tickets with deal value map to Freshsales Deals with the ticket amount as deal value; support-oriented tickets map to Cases. The routing rule is documented in the object mapping matrix before migration. Ticket status, priority, due dates, and internal notes migrate as deal or case fields respectively.

Bluetrait Ticket conversations (internal notes and customer replies) migrate to Freshsales Activity records (Tasks or Emails) linked to the resolved Deal or Case. We preserve the conversation timestamp and author, but ticket-to-case threading is maintained by linking to the Case record rather than a flat conversation view.

Freshsales has no native timesheet module. Bluetrait Timesheet entries (date, hours, user, task/project link, timesheet type) map to Freshsales Tasks with custom fields for hours, billable flag, and project reference. We create these custom Task fields before migration. If the customer uses timesheet data for billing, they should set up a separate timesheet tool post-migration; Freshsales does not have recurring billing from time entries.

Bluetrait Projects link to timesheets, budgets, and tasks. If Projects represent billable work streams, we map them to Freshsales Deals with a custom project reference field. If Projects represent internal work tracking, we map them to a Freshsales Custom Object created during schema setup. Project budgets and task counts migrate as custom fields on the chosen destination object.

Bluetrait Products (with quantities, recurring billing frequencies, and pricing) map to Freshsales Products. Product pricing and recurring billing cadence migrate as Product fields. Subscription cadence requiring ongoing billing management is flagged as out-of-scope for Freshsales migration because Freshsales does not have a native subscription management module.

Bluetrait Invoices, Quotes, and Purchase Orders do not have a native Freshsales equivalent because Freshsales lacks a billing or invoicing module. Open and historical invoices transfer as static records (exported as CSV and imported as Freshsales Notes or document attachments on the relevant Account). Recurring billing automation rules are documented in the handoff package for manual re-setup in a billing tool post-migration.

Bluetrait Users map to Freshsales Users by email match. We resolve each Hubspot Owner or agent to the corresponding Freshsales User. Users without a Freshsales match go to a reconciliation queue for the customer's admin to provision. Two-Factor Authentication status is noted but cannot be migrated; users reset 2FA in Freshsales at first login.

Bluetrait knowledge-base articles export via CSV but lose their ticket linkage during migration. We export articles and their categories as a structured document and deliver it as part of the handoff package. Article-to-ticket associations are listed in a separate reference sheet for the customer to re-link in Freshsales Articles or a linked knowledge-base tool.