Migrate from Bolten CRM to Pipedrive

Bolten Contact records map directly to Pipedrive Person. Name, phone, email, and address fields migrate 1:1. Custom properties on the contact migrate to Pipedrive custom fields on Person, with type conversion applied (Bolten multi-select maps to Pipedrive multi-select picklist, date to date field, etc.). Tags on Bolten contacts migrate to Pipedrive labels on the Person record.

Bolten Lead records map to Pipedrive Lead with lifecycle status, source campaign attribution, and owner assignment preserved. Bolten's lead origin tracking (Google Ads, Meta Ads, direct) migrates to Pipedrive Lead custom fields for attribution reporting. Owner mapping resolves by email match against Pipedrive users.

Bolten Deals map to Pipedrive Deals with pipeline stage names and values. Critical: Bolten allows free-text stage names with no enforced ordering in the API. We capture the customer-confirmed stage ordinal sequence during pre-migration mapping and write explicit stage order to Pipedrive's pipeline stages before Deal import. Probability percentages migrate from Bolten stage settings to Pipedrive stage probability.

Each Bolten Project's Kanban funnel becomes a Pipedrive Pipeline. We configure stage names, stage order, and probability percentages in Pipedrive before Deals import. If multiple Bolten Projects contain Deals, we create separate Pipedrive Pipelines (or separate Pipedrive accounts if the business logic requires full workspace separation) based on the customer's scoping choice.

Bolten Tasks migrate to Pipedrive Tasks with assignee, due date, status, and linked contact or deal association preserved. Task linkage to Bolten contacts and deals is resolved via external ID mapping during Pipedrive import. Recurring task rules do not transfer; we flag them in the migration inventory for manual rebuild.

Bolten's change-audit log (every record edit, assignment change, and stage move) migrates as chronological Note records attached to the relevant Person, Lead, Deal, or Organization in Pipedrive. Each Note records the timestamp, operator, and change description from Bolten. The audit trail is preserved as a historical reference feed rather than a structured activity log.

Bolten custom fields (text, number, date, dropdown, multi-select) map to Pipedrive custom fields of the corresponding type on the relevant entity. Pipedrive does not allow field type changes after creation: if a Bolten text field contains numeric data but was typed as text, we preserve it as a text field in Pipedrive rather than attempting type conversion. Customers choosing to consolidate similar fields into formula fields handle that as a post-migration configuration step.

Bolten's Conversion tracking (utm-source, utm-medium, conversion events, campaign attribution) migrates to Pipedrive as custom fields on the Lead and Person records. Pipedrive does not have a native conversion attribution model; UTM values and campaign source data are stored as text fields for reporting in Pipedrive's Insights module or exported to a BI tool.

Bolten Users map to Pipedrive Users by email match. We extract every distinct user referenced on Contacts, Leads, Deals, and Tasks and reconcile against the destination Pipedrive account's user list. Suspended or inactive Bolten users are flagged for remapping to active destination users or archived status in Pipedrive.

Bolten flat-label tags applied to contacts and deals migrate to Pipedrive Labels on the Person, Lead, and Deal records. Tag sets are preserved as a flat list; Pipedrive Labels do not support hierarchical tag structures. If a customer used Bolten tags as a pseudo-category system, we advise on label group strategy during scoping.

Bolten does not have a dedicated Organization/Company object. If the customer's workflow uses Bolten contacts to represent both individuals and companies (common in simpler CRM setups), we split them during migration: company-level data migrates to Pipedrive Organization, individual contact data migrates to Pipedrive Person linked to the Organization. The customer confirms the split logic during scoping.