Migrate from Barantum CRM to Salesforce Sales Cloud

Barantum Contact records map directly to Salesforce Contact with standard fields (FirstName, LastName, Email, Phone, Title) preserved. WhatsApp profile linkage data stored in Barantum contact extensions migrates to a custom field whatsapp_profile_url__c. We migrate contacts first because all other objects (Deals, Tickets, Activities) carry a contact reference. Any duplicate contacts detected by email match are flagged in a reconciliation report for the customer admin to resolve before insert.

Barantum Company records map to Salesforce Account. The Barantum company name becomes Account Name, and any website field maps to Account Website. We preserve the company-contact relationship by importing Accounts before Contacts and resolving the AccountId on each Contact at migration time using name-matching or an explicit company_id field. Accounts are created as Household type if the Barantum data structure indicates B2C rather than B2B relationships.

Barantum Deals map to Salesforce Opportunity with stage, value, owner, and expected close date preserved. The pipeline stage name in Barantum does not map 1:1 to Salesforce StageName; we build an explicit mapping table during scoping that the customer approves before migration. Barantum deal_owner maps to Salesforce OwnerId via the User email resolution. Closed-Lost and Closed-Won reason fields from Barantum custom properties become Salesforce Loss Reason and Win Reason field values.

Each Barantum pipeline stage becomes a Salesforce StageName entry in a Sales Process that we configure during schema design. Stage probability percentages transfer from Barantum to Salesforce StageProbability, rounding to the nearest integer Salesforce accepts. If Barantum uses multiple pipelines, we create separate Record Types on Opportunity, each with its own Sales Process and Page Layout, so stage values stay scoped per line of business.

Barantum Lead records (captured via forms, imports, or chatbot interactions) map to Salesforce Lead. Lead source, status, and any custom scoring fields migrate to corresponding Salesforce Lead fields or custom fields if no direct equivalent exists. We flag any Barantum Leads that have already been converted to Contacts in Barantum to prevent duplicate Contact creation during migration; these are skipped or merged based on the customer's preference.

Barantum customer service Tickets migrate to Salesforce Case if the destination Salesforce org includes Service Cloud or if the customer adds it as part of the migration scope. Ticket pipeline becomes Case Record Type, ticket status values become Case Status picklist entries, and linked agent assignment migrates to Case Owner via the User mapping. Conversation histories attached to Barantum Tickets migrate as EmailMessage records linked to the Case, preserving agent attribution and timestamps.

Barantum Meeting records (title, scheduled time, attendees, outcome notes) map to Salesforce Event. StartDateTime, EndDateTime, and Location transfer directly. Attendees link via EventRelation records pointing to the resolved Contact, Lead, or User. Recurring meeting series in Barantum are enumerated during discovery; if the source supports series export, we map to Salesforce RecurrencePattern and recreate the series as individual Event records with the recurrence pattern metadata attached.

Barantum Activity logs (call logs, notes, and task completions tied to contacts or deals) map to Salesforce Task. Each activity type from Barantum is enumerated during discovery and mapped to a Salesforce Task with the appropriate TaskSubtype. Activity timestamps are preserved in ActivityDate for timeline ordering. Task Status and Priority transfer from Barantum's activity status and urgency fields. We map barantum_activity_type to a custom field original_activity_type__c to preserve the source system context.

Barantum WhatsApp and omnichannel chat threads are stored as linked conversation threads inside Contact records. We extract each thread as a Salesforce Task record (TaskSubtype = Task, with a custom field chat_channel__c set to 'WhatsApp' or the relevant channel) and attach the conversation text as a Note linked via ContentDocumentLink to the parent Contact. Media files (images, documents) shared in chat are downloaded as files and migrated as ContentDocument records attached to the Contact. This is the highest-severity mapping step; we run a contact-count-to-conversation-count reconciliation check after migration to catch any orphaned threads.

Barantum VoIP call center logs include call direction (inbound/outbound), duration, agent extension, and recording links. We map these to Salesforce Task with TaskSubtype = Call, and map the extended metadata to custom fields: call_direction__c, call_duration_seconds__c, agent_extension__c, and recording_url__c. Call disposition codes from Barantum migrate to a custom call_disposition__c picklist field. Audio recordings are downloaded as files and migrated as ContentDocument records attached to the Task.

Barantum user and agent accounts (name, email, role, extension) are exported for owner/agent mapping. We do not create new Salesforce User seats; instead we map Barantum user IDs to existing Salesforce Users by email match. Any Barantum user without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Agent extension numbers migrate to a custom user field for call center routing if Sales Cloud Voice is deployed.

Custom fields added to any Barantum object (contacts, deals, tickets, companies) are enumerated during discovery and mapped to Salesforce custom fields of matching data type. We pre-create the destination custom fields (with __c suffix per Salesforce convention) and their field-level security settings before any data import. Multi-select picklists, date fields, and numeric fields map to Salesforce equivalents; any Barantum data type without a direct Salesforce equivalent is mapped to a Textarea or Text field and flagged in the mapping document for the admin to refine post-migration.