Migrate from Bolten CRM to Salesforce Sales Cloud

Bolten Contacts map directly to Salesforce Contact. We extract name, phone, email, address, and any custom properties per contact. Tags applied to Bolten contacts migrate to a Salesforce multi-select picklist field (or Topic via TopicAssignment if the customer prefers a taxonomy model). Lead-source attribution stored on the Bolten contact migrates to Salesforce LeadSource on the Contact record. Suspended or inactive Bolten contacts are flagged during extraction and held in a reconciliation queue for the customer's admin to confirm before import.

Bolten Leads map to Salesforce Lead with lifecycle status, source campaign, and owner assignment preserved. The Bolten lead's assigned owner resolves to a Salesforce User by email match during import. Any Bolten Lead with a lifecycle status value not matching a Salesforce Lead Status picklist entry is flagged for custom picklist value creation before migration. The customer confirms the mapping between Bolten lifecycle stages and Salesforce Lead Status during scoping.

Bolten Deals map to Salesforce Opportunity. The most migration-critical step is resolving the stage sequence: Bolten allows arbitrary Kanban stage names with no enforced ordering property in its API. During pre-migration scoping we ask the customer to confirm the intended stage order (which stage is first, which is last, what are the closed-won and closed-lost stages) and we write the ordinal position explicitly to the Salesforce Opportunity stage sequence. Deal value, deal name, expected close date, and associated contact owner migrate 1:1.

Each Bolten Kanban stage becomes a Salesforce StageName value within a Sales Process. We configure a Salesforce Record Type for the Opportunity object and create a corresponding Sales Process that whitelists only the Bolten stages the customer confirms are in use. Stage probability percentages migrate from Bolten (if set) to Salesforce StageProbability, rounded to the nearest allowed integer.

If the customer uses multiple Kanban pipelines in Bolten (for different lines of business or client workspaces), each pipeline maps to a Salesforce Record Type on Opportunity. Each Record Type gets its own Page Layout and Sales Process so stage values remain scoped per pipeline and do not bleed across business units.

Bolten Tasks carry assignee, due date, status, and a linked contact or deal. We migrate Tasks with their association intact via WhoId (Contact or Lead) and WhatId (Opportunity) resolved at migration time. Recurring task rules do not transfer and are flagged in the handoff document for the customer's admin to rebuild as Salesforce Flow recurring actions if needed.

Bolten logs a full change-audit history per record (every edit, assignment, and stage move). We migrate this as a chronological feed of Task records attached to the parent Contact, Lead, or Opportunity with ActivityDate set to the original Bolten timestamp and a custom field audit_action__c describing the change (e.g., stage_moved, owner_changed, field_updated). This preserves the timeline without requiring the customer to purchase Salesforce Field Audit Trail.

Bolten's Conversions add-on tracks lead origin (Google, Meta Ads, direct) and real-time conversion events. We migrate conversion records as custom fields on the Salesforce Lead (e.g., utm_source__c, utm_medium__c, conversion_date__c) populated from the Bolten export. If UTM values are present in Bolten's custom fields, they transfer as-is. The customer may need to re-link analytics attribution in their reporting tool post-migration.

Bolten custom fields (text, number, date, dropdown, multi-select) map to equivalent Salesforce custom fields by type. Multi-select in Bolten maps to Multi-Select Picklist in Salesforce. Dropdown maps to Picklist. We pre-create the destination schema in Salesforce (field label, API name, type, picklist values) before any data import. Any Bolten custom field with no corresponding Salesforce target is flagged during scoping for the customer to confirm whether a new Salesforce field is needed or the data should be excluded.

Bolten Users are identified by email and name. We map source-user email to destination-user email during import. Suspended or inactive Bolten users are flagged for remapping to an active destination User. The customer's Salesforce admin provisions any missing Users before record import begins because OwnerId references on Opportunity and Task require a valid Salesforce User ID.

Bolten tags are flat-label strings applied to contacts and deals. We migrate tag sets as a Salesforce multi-select picklist field on Contact and Opportunity. Alternatively, if the customer prefers a taxonomy model, we migrate tags to Salesforce Topics with TopicAssignment records linked to the relevant records. The customer chooses the tag strategy during scoping.

Bolten WhatsApp conversations are stored on Meta's servers, not Bolten's own database. Direct migration of WhatsApp message content is not technically possible. We migrate the contact phone number, conversation start timestamp, and most recent message timestamp as a Task record with a custom field whatsapp_metadata__c containing the JSON payload (phone, last_message_time, message_count). The customer must separately request WhatsApp message history from Meta via Meta's data portability tool. This limitation is disclosed to the customer before migration scoping begins.