Migrate from Barantum CRM to Zoho CRM

Barantum Contact records map directly to Zoho CRM Contacts. Standard fields (First Name, Last Name, Email, Phone, Mobile, Address) migrate 1:1. WhatsApp profile linkage stored on Barantum contacts is not a native Zoho field; we extract it as a custom multi-line text field wa_profile_link__c or map it to Zoho's Additional Email field if the customer prefers a standard location. We run a contact-count reconciliation after migration to confirm every Barantum contact has a corresponding Zoho Contact record.

Barantum Company records map to Zoho Accounts. The company name becomes the Account Name, domain becomes Website, and address fields map to the standard address compound. Barantum does not enforce a strict account-contact relationship in the same way Zoho does; we resolve this by matching Barantum contacts with a populated Company field to Zoho Accounts by name during import, creating the Account first so the Contact.AccountId lookup is satisfied at insert time.

Barantum Deals map to Zoho Deals with a configurable stage translation table created during scoping. The Barantum pipeline assignment translates to a Zoho Deal Field Pipeline. Deal value, expected close date, owner, and notes migrate directly. Closed-won and closed-lost reasons in Barantum become custom picklist fields in Zoho if they exist, or are stored in the Notes field if no matching Zoho field is available. We create the Zoho pipeline structure before Deal import so that all stage values are valid at insert time.

Barantum Lead records (captured via forms, imports, or chatbot) map to Zoho Leads. Lead source, status, and any scoring or qualification fields migrate to Zoho Lead custom fields. Barantum's lead-conversion action (converting a Lead to a Contact and Company) does not need to fire during migration; we migrate Leads as-is and let the customer's Zoho admin run conversions post-migration if needed.

Barantum Tickets map to Zoho Desk Tickets if the customer licenses Zoho Desk alongside CRM, or to Zoho CRM Cases if Desk is not in scope. Ticket status, priority, assigned agent, and conversation history migrate as linked Notes or EmailMessage records. Agent assignment resolves by matching Barantum agent email to Zoho User email. Barantum ticket pipelines (if used) map to Ticket Status values in Zoho Desk.

Barantum Meeting records map to Zoho Events with Title, Start Date Time, End Date Time, Location, and attendee list preserved. Recurring meetings in Barantum are enumerated individually and migrated as separate Event records; Zoho's recurring event pattern is not applied automatically because recurrence rules differ between platforms.

Barantum Activity logs (call logs, notes, task completions) map to Zoho Tasks. Activity type enumeration happens during discovery; each discovered Barantum activity type becomes a Zoho Task.Subject prefix or a custom picklist field act_type__c so that call logs, notes, and generic tasks remain distinguishable post-migration. Activity timestamps and owner assignments migrate directly.

Barantum WhatsApp conversation threads stored on Contact records are extracted as separate migration artifacts and mapped to Zoho Notes attached to the corresponding Contact, or to Activity Task records if the customer prefers a chronological timeline. Each thread is deduplicated against the contact's conversation count to catch orphaned threads. Media file references migrate as URLs in the Note body or as linked attachments. This is the highest-severity data coupling issue in this migration pair; we validate contact count against conversation count as a post-migration reconciliation check.

Barantum VoIP call center logs (direction, duration, agent extension, recording link) map to Zoho CRM Tasks with TaskSubtype = Call. Call duration, disposition, and recording URL migrate to custom Task fields call_duration__c, call_disposition__c, and call_recording_url__c. We map Barantum agent extensions to Zoho User email lookups so that the correct owner is assigned to each call record.

Barantum User and Agent records (name, email, role, extension) are enumerated during discovery for owner mapping purposes. We do not create new Zoho User seats in the destination; instead we map Barantum agent IDs to Zoho User records by email match. Any Barantum agent without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import begins.

Barantum custom fields on contacts, deals, tickets, or other objects are enumerated during discovery. We export all custom field values and map them to Zoho CRM custom fields of matching data type, creating the destination custom field in the appropriate module first via Zoho's field API. Zoho Standard Edition does not include custom fields; we recommend Professional or above for customers with heavy custom field usage. Custom field limits in Zoho (300 per module, 5 lookup fields) are checked against the migration scope during scoping.