Migrate from Barantum CRM to Pipedrive

Barantum Contact records map directly to Pipedrive Person. Standard fields (name, phone, email, address) migrate 1:1. WhatsApp profile linkage stored in Barantum as a linked sub-object is extracted separately as a note or activity (see Chat Conversations mapping). We preserve any Barantum contact owner as the Person's OwnerId by email match. If Barantum custom fields exist on Contact, we create matching Pipedrive custom fields of equivalent type before migration.

Barantum Company records map to Pipedrive Organization. The company name becomes the Organization name and serves as the dedupe key. We migrate company address, industry, website, and any custom fields. Organization is created before Contact import so that the Organization-Person relationship is satisfied at import time.

Barantum Deal records map to Pipedrive Deal with stage, value, owner, and expected close date preserved. Pipeline stages in Barantum (which may use custom stage names like 'Hot Prospect', 'Proposal Sent', 'Negotiation') are mapped to Pipedrive Deal stages during scoping. Barantum does not expose multiple deal pipelines via API; if the customer has configured multiple pipelines in Barantum, we enumerate them during discovery and create corresponding Pipedrive pipelines (Growth tier and above).

Barantum Lead records map to Pipedrive Lead. Lead source, status, and any scoring values from Barantum custom fields migrate to Pipedrive custom fields on Lead. Barantum Lead conversion history (the record of when a Lead became a Contact) does not export via API; we document this as a data gap and recommend the customer capture any required conversion timestamps from Barantum reports before the migration window.

Barantum Tickets map to Pipedrive Activities (type=task with subject and notes) or, if the customer uses Pipedrive's separate Products module for service tracking, to Product-linked activities. Ticket status (Open, In Progress, Resolved, Closed) maps to Pipedrive Activity status (open, completed). Ticket conversation history migrates as linked notes with timestamp and agent attribution. If the customer requires a ticketing system equivalent, we recommend Pipedrive's optional Products module or a separate helpdesk integration (Zendesk, Freshdesk) post-migration.

Barantum Meeting records map to Pipedrive Activities with type=calendar_event. Title, scheduled time, attendees (as Person or Organization links), location, and outcome notes migrate directly. Recurring meetings in Barantum are enumerated during discovery; we migrate the series as individual activity records and document the recurrence pattern for manual reconstruction in Pipedrive Calendar or a connected calendar tool.

Barantum call logs (VoIP call center) map to Pipedrive Activities with type=call. Call direction (inbound/outbound), duration, agent extension, disposition, and recording links migrate as custom fields on the activity. Call recordings are downloaded as audio files and attached to the activity as a note with a reference link. If the customer uses call recording storage in Barantum, we flag the storage location during scoping.

Barantum WhatsApp chat threads stored as linked conversation text on contact records are extracted as separate note records and attached to the corresponding Pipedrive Person. Each note captures: conversation text, timestamp, agent attribution (which Barantum user sent or received), and media file references. Media files are downloaded and attached as separate files to the Person record. This is the highest-risk mapping in the migration because Barantum stores threads as nested JSON within the contact profile; we run a contact-count-to-conversation-count reconciliation check after extraction to catch orphaned threads.

Barantum User and Agent records map to Pipedrive User. We resolve Barantum agent email to Pipedrive User email as the dedupe key. Any Barantum role (admin, agent, manager) maps to Pipedrive permission sets. Barantum extension numbers for the VoIP call center migrate as a custom field on the Pipedrive User record. If a Barantum user has left the company and the account is inactive, we map to an inactive Pipedrive User and flag for the customer's admin to archive or reassign.

Barantum custom fields on contacts, companies, deals, tickets, or other objects are enumerated during discovery. We create matching Pipedrive custom fields of equivalent data type (text, number, date, picklist, checkbox, phone, email, address) before migration begins. Pipedrive custom field availability varies by tier: Important fields require Growth ($29/user), Required fields and pipeline-specific fields require Premium ($59/user). We include tier requirements in the custom field inventory delivered before migration.

Barantum workflow automation rules (auto-assignment, auto-reply, SLA timers, chatbot triggers) are configured in-platform and not exposed through Barantum's public API. We do not migrate them as executable code. During discovery we enumerate every discovered Barantum workflow and document it in a written workflow audit worksheet: trigger type, conditions, actions, and a recommended Pipedrive Automation Rule equivalent (or Power Automate flow if the complexity exceeds Pipedrive's native Automation Rules). The customer's Pipedrive admin or automation partner rebuilds them post-migration.