Migrate from Bluetrait to Pipedrive

Bluetrait Client records carry both individual contact data and a loosely-associated Company reference. We split this into Pipedrive Person (name, email, phone, address) and Organization (company name, domain, industry) during migration, creating the Organization first as the parent so that the Organization ID is available for the Person's org_id field. If a Bluetrait Client has no meaningful company association, we create a single Person record and link it to an Organization named after the client's email domain or a 'Standalone' placeholder to satisfy Pipedrive's relational model.

Bluetrait Company records map directly to Pipedrive Organization. The company name becomes Organization name, address fields map to Organization address fields, and any CRM custom properties on the Company become custom fields on the Organization. We use company name as the dedupe key during import. Company-Client associations in Bluetrait resolve into Organization-Person relationships in Pipedrive by matching the client_company_id foreign key from each Client record.

Bluetrait Tickets map to Pipedrive Activity records with type Note, containing ticket subject, status, priority, assignee, and a concatenated body of the ticket's internal notes and conversation history. If a ticket represents a billable work item or an opportunity worth tracking in a pipeline, we optionally map it to a Pipedrive Deal with the ticket ID stored in a custom field for traceability. Ticket custom fields and tags migrate as custom fields and labels on the Activity or Deal.

Bluetrait Timesheet entries include date, hours, user, task/project link, and timesheet type. Pipedrive has no native timesheet object. We create Pipedrive Activity records of type Note with custom fields timesheet_date__c (date), timesheet_hours__c (decimal), timesheet_type__c (picklist), and project_reference__c (text). The activity is linked to the Person and Organization representing the relevant client. We preserve the relationship between timesheet entries and tickets by storing the originating ticket ID in a custom field on the Activity.

Bluetrait Projects link to timesheets, budgets, and tasks. We map project names and budget figures as custom fields on a parent Activity or as a labelled Deal with the project status stored in a custom field. Custom project statuses and budget thresholds become custom picklist fields on the destination record. Since Pipedrive does not have a native project object, we consolidate project metadata under a single Activity per project for reference.

Bluetrait invoices, quotes, and purchase orders migrate as Pipedrive Deal records with invoice metadata (invoice number, line items, tax, payment status) stored as custom fields and a PDF reference URL if the source export includes file attachments. Open and historical invoice status migrates as a custom field. Recurring billing automation rules do not migrate; we document each recurring billing configuration we encounter as a written handoff item for the customer's admin to re-implement in their chosen billing tool.

Bluetrait Products with quantities, recurring billing frequencies, and pricing map to Pipedrive Products. ProductCode maps from the Bluetrait SKU if present. Recurring billing cadence and subscription frequency become custom fields on the Pipedrive Product since Pipedrive Products do not natively support subscription management.

Bluetrait Agents are MSP-specific endpoint records with watchdog status, installed software lists, and alert configurations. These are RMM data points that have no equivalent in Pipedrive's sales CRM schema. We do not migrate agent records. We provide a written inventory of all agent endpoints encountered, their associated client organizations, and their last-seen status as a reference document for the customer's MSP tooling decision. If the customer is also moving their RMM tool separately, that migration is outside this scope.

Bluetrait Users map to Pipedrive Users by email address match. We extract username, role, and permissions group and store role as a custom field pipedrive_user_role__c since Pipedrive User records do not have a native role description field. Two-Factor Authentication status is noted in the migration workbook but cannot be transferred. Users without a matching email in the destination Pipedrive account are placed in a reconciliation queue for the customer to provision before record import resumes.

Bluetrait Knowledge Base articles can be exported via CSV including article body, category, and ticket associations. Pipedrive does not have a native knowledge base feature; articles would require a separate knowledge base tool. We export articles as a structured CSV inventory (title, body, category, associated ticket IDs) and a written reference document for the customer to import into their chosen knowledge base platform (Notion, Confluence, or a dedicated KB tool). Article-to-ticket linking is documented separately for manual re-association.

Bluetrait's Passwords module stores credentials for managed client systems. These are not accessible via API or CSV for security reasons and cannot be migrated. We generate a full inventory of password entries (name, associated client, folder structure, last updated) as a reference document. The customer manually recreates entries in their destination password manager post-migration. This is not a migration blocker but requires post-cutover work on the customer's side.

Bluetrait's CRM module includes Lead records with lead status, lifecycle stage, and contact details. These map directly to Pipedrive Lead records using the email address as the dedupe key. Lead status from Bluetrait becomes a custom field lead_status_source__c on the Pipedrive Lead; lifecycle stage maps to a custom field lifecycle_stage__c. Pipedrive's own Lead statuses (New, Contacted, Qualified, Unqualified) are set according to the customer's chosen stage mapping during scoping.