Migrate from Barantum CRM to Freshsales

Barantum Contact records (name, phone, email, profile details, WhatsApp linkage) map directly to Freshsales Contact. We preserve the Barantum contact ID as an external_id field for reconciliation. WhatsApp-linked profile data is separated from the contact profile and migrated as linked Activity records (see Chat Conversations mapping). Email and phone serve as dedupe keys during import; any duplicates are flagged for admin resolution before final commit.

Barantum Company records serve as parent entities grouping related contacts. They map to Freshsales Account with the company name, address, industry, and any custom fields preserved. We import Accounts first to satisfy the lookup relationship required when importing Contacts. If Barantum company-contact relationships use name-matching rather than explicit foreign keys, we resolve the Account-Contact linkage by company name lookup before Contact insert.

Barantum Deals track sales opportunities with stage, value, owner, expected close date, and product line items. We map each Barantum pipeline to a Freshsales Deal pipe and create a stage-mapping table during scoping so that Barantum stage labels translate to Freshsales stage values. Deal amount is stored in Indonesian Rupiah; we apply the customer's specified exchange rate at migration time and store the original currency value in a custom field for audit. Owner maps by email to Freshsales User.

Barantum Leads (captured via forms, imports, or chatbot interactions) map to Freshsales Lead with lead source, status, and custom fields preserved. The Barantum lead_status field maps to Freshsales Lead Status. We flag any Barantum leads that have already been converted to Contacts and ensure the Freshsales Lead conversion mapping (Lead to Contact, Account, and Deal) is configured before migration so that converted leads do not lose their association data.

Barantum Tickets store customer service issues with description, status, assigned agent, and conversation history. They map to Freshsales Ticket with subject, description, status, priority, and agent assignment. Barantum ticket pipeline stages map to Freshsales Ticket statuses. Agent assignment resolves by email to Freshsales User. Ticket conversation transcripts migrate as linked Notes or Activities depending on the customer's preference for activity timeline versus a threaded view.

Barantum Meeting records (title, scheduled time, attendees, outcome notes) map to Freshsales Meeting. Start time, end time, location, and outcome preserve. Attendees resolve by email to Freshsales Contacts or Leads. Recurring meetings in Barantum are enumerated as individual Meeting records and imported as a series with the recurrence pattern documented in a custom field for manual reconstruction in Freshsales calendar if needed.

Barantum Activity logs (call logs, notes, task completions tied to contacts or deals) map to Freshsales Activity records. We enumerate available Barantum activity types during discovery and map each to a Freshsales Activity type (Task or Event). Activity timestamp, description, and owner migrate. Activities without a resolved parent record (Contact, Deal, or Account) are held in a staging queue and linked after parent record migration completes.

This is the highest-severity mapping step. Barantum stores WhatsApp conversation threads embedded in contact profile records as linked conversation data. Freshsales does not embed chat threads in the contact profile. We extract every conversation thread, timestamp it to the original message date, and insert it as a Freshsales Activity record (type Note or Task depending on configuration) linked to the Contact. We run a reconciliation check comparing Barantum contact count to migrated activity records to catch orphaned threads. Media files from WhatsApp (images, documents) are downloaded and attached as Freshsales Attachments linked to the parent Activity.

Barantum VoIP call center logs (direction, duration, agent extension, recording links) map to Freshsales Call records. Call disposition, duration in seconds, and recording URL migrate to custom Call fields. Agent extension resolves by email to Freshsales User for ownership. Call recordings are downloaded as audio files and attached to the Call record as file attachments. If Freshsales is on a lower tier without native call logging, call records migrate as Tasks with call subtype and custom duration fields.

Barantum User and agent accounts (name, email, role, extension) are exported for owner mapping. We resolve each Barantum agent by email against Freshsales User records. Any Barantum owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record migration proceeds. We do not create Freshsales user seats as part of the data migration; that is an administrative step the customer controls to match their actual seat count.