Migrate your Barantum CRM data

Contact records in Barantum include name, phone, email, profile details, and WhatsApp profile linkage. We migrate contacts 1:1 with all standard fields preserved. WhatsApp-linked profile data is mapped to a custom property in the destination if the target CRM does not natively support WhatsApp associations.

Company records serve as parent entities that group related contacts. We preserve company-contact relationships by migrating companies first, then linking contacts via name-matching or explicit company ID fields during the child-object migration phase.

Deals track sales opportunities with stage, value, owner, and expected close date. Pipeline stages in Barantum may not map 1:1 to destination pipeline stages; we create a mapping table during scoping and allow customers to confirm stage alignment before import.

Leads are captured via forms, imports, or chatbot interactions and can be converted to Contacts. We export lead records with their source and status fields, mapping Lead_Status to a custom property in CRMs that do not have a separate Lead object.

Customer service tickets store issue description, status, assigned agent, and conversation history. We export full ticket records including linked chat transcripts and agent assignments. Destination ticket fields are mapped individually to match the target system's ticket schema.

Meeting records include title, scheduled time, attendees, and outcome notes. We export meetings as calendar entries or activity records depending on destination schema compatibility. Recurring meeting series are expanded into individual records unless the destination supports series-native import.

Activity logs record call logs, notes, and task completions tied to contacts or deals. Barantum activity types vary by configuration; we enumerate available activity types during discovery and map each to the corresponding activity or engagement object in the destination.

WhatsApp and omnichannel chat histories are stored as linked conversation threads on contact records. We export conversation text, timestamps, agent attribution, and media references. Media files are downloaded separately and re-uploaded as attachments in the destination CRM.

VoIP call center logs include call direction, duration, agent extension, and recording links. Call recordings are downloaded as audio files and migrated as linked attachments. We map call disposition codes to destination activity or task outcome fields.

User and agent accounts include name, email, role, and extension. We export user records for owner/agent mapping but do not create new user seats in the destination; instead we map agent IDs to corresponding user records or leave owner fields to be reassigned post-migration.

Custom fields added to contacts, deals, tickets, or other objects are enumerated during discovery. We export all custom field values and map them to destination custom fields of matching data type, creating new custom fields in the destination if they do not already exist.