Migrate from Bolten CRM to Freshsales

Bolten Contact records map directly to Freshsales Contact. Standard fields (name, phone, email, address) migrate 1:1. Custom fields on Contact (text, number, date, dropdown, multi-select) map to Freshsales custom contact fields of the equivalent type. Tags stored on the Bolten Contact migrate as Freshsales contact tags or as multi-select custom fields depending on the customer's tagging strategy decision during scoping.

Bolten Lead records migrate to Freshsales Lead with lifecycle status, source campaign attribution, and owner assignment preserved. Bolten's lead-source tracking (Google Ads, Meta Ads, direct) maps to Freshsales lead source field. Owner resolution is by email match against Freshsales Users. Suspended or inactive Bolten users are flagged for remapping to active destination users before Lead import begins.

Bolten Kanban Deals map to Freshsales Deals with one critical transformation: Bolten allows arbitrary free-text stage names with no enforced ordering in the API. We ask the customer to confirm the intended stage sequence during pre-migration mapping and write an explicit ordinal position to Freshsales pipeline stage order before import. Closed-Lost and Closed-Won deal status migrates to Freshsales deal stage. Deal value and currency fields transfer directly.

Each unique Bolten Kanban stage name becomes a Freshsales pipeline stage. We create the pipeline in Freshsales Admin > Pipeline before migration, assign the correct stage order based on customer confirmation, and set stage probabilities that match the customer's historical Bolten win/loss data. This configuration step is required before any Deal records are imported.

Bolten Tasks migrate to Freshsales Tasks with assignee, due date, status, and linked contact/deal preserved. Task associations resolve by looking up the contact and deal record by their migrated IDs. Recurring task rules do not transfer; we document which tasks have recurrence patterns so the customer can rebuild them as Freshsales task automation post-migration.

Bolten's full change-audit history per record (every edit, assignment, and stage move with timestamp and operator) migrates as a chronological activity feed per record in Freshsales. Each audit entry becomes a timestamped Note or Activity record attached to the parent Contact, Lead, or Deal. We preserve the operator (user) reference by resolving email to the migrated User record.

Bolten Users are identified by email and name. We map source-user email to destination-user email during import. Any Bolten user referenced on a record but not yet provisioned in Freshsales is held in a reconciliation queue for the customer to resolve before record import continues. Inactive Bolten users are flagged separately for remapping decision.

Bolten flat-label tags on Contacts and Deals migrate to Freshsales tags. Where tags represent categorical data (e.g., industry, segment, product interest), we offer the option to map them to Freshsales multi-select custom fields during scoping so they are filterable in Freshsales reports and segmentations.

WhatsApp message bodies live on Meta's infrastructure and cannot be exported via Bolten's database. We migrate the contact phone number (already mapped as part of Contact), conversation timestamps, and any conversation metadata Bolten exposes via its API as Activity records on the Contact. This preserves that a conversation occurred without attempting to move the actual message content.

Bolten tracks lead origin (Google Ads, Meta Ads, direct) and real-time conversion events via its Conversions add-on. We migrate attribution data as Freshsales lead source values and, where Bolten stores utm_source and utm_medium, as custom fields on the Lead record. The customer confirms the attribution model during scoping to ensure the mapping aligns with how they report on lead quality.