Migrate from Barantum CRM to Nutshell

Barantum Contact records map 1:1 to Nutshell Person. Standard fields (name, phone, email, address) migrate directly. The critical migration step is handling Barantum's WhatsApp profile linkage, which stores WhatsApp number and blue-tick status on the contact record. We extract WhatsApp number as a secondary phone field in Nutshell. The WhatsApp profile verification status does not have a native Nutshell equivalent and is recorded as a custom checkbox field for the customer's admin to reference post-migration.

Barantum Company records map to Nutshell Account. The company name, domain, industry, and address fields migrate directly. Barantum's Indonesian-localized address format (kecamatan, kota, provinsi) is mapped to Nutshell's standard address fields with a custom field retaining the original administrative division for audit. Parent-company hierarchies from Barantum map to Nutshell's Account parent relationship if the destination Account model uses hierarchy.

Barantum Deal records map to Nutshell Deal. The deal name, value, stage, owner, and expected close date migrate directly. Pipeline stage mapping requires a custom stage translation table because Barantum pipeline stages (often labeled in Indonesian or configured by the customer) must map to Nutshell's default or customer-configured Deal stages. We enumerate available stages during discovery and create the mapping table before migration runs.

Barantum Ticket records require a structural decision during scoping because Nutshell has no native ticket object. The recommended approach maps each Barantum Ticket to a Nutshell Task with the task subject prefixed with 'Ticket:'. Ticket status (open, pending, resolved) maps to Nutshell Task status, and ticket conversation history migrates as a linked Note or Activity log entry on the Task. For teams requiring full ticket preservation, we document the use of a third-party Nutshell-integrated helpdesk (such as Zendesk or Help Scout) as the ticket management layer post-migration.

This is the highest-severity mapping step. Barantum stores WhatsApp and omnichannel chat threads as embedded records on Contact, with conversation text, timestamps, agent attribution, and media references stored together. Nutshell has no native messaging or chat object. We export each conversation thread as a separate Note record linked to the corresponding Person, with a custom field chat_source__c set to 'WhatsApp' or 'omnichannel' to preserve origin context. Media files (images, documents shared in chat) are downloaded and attached as Note attachments or stored in a shared media reference field for the customer to re-upload if needed.

Barantum VoIP call center records (call direction, duration, agent extension, disposition, recording URL) map to Nutshell Activity records. Call recording audio files are downloaded from Barantum and re-attached as Activity attachments in Nutshell. The call duration maps to a custom numeric field call_duration_seconds__c since Nutshell Activity does not natively store duration in seconds. Call disposition from Barantum's agent notes migrates as an Activity note.

Barantum Meeting records (title, scheduled time, attendees, outcome notes) map to Nutshell Activity records. Nutshell does not have a native meetings object, so meetings appear as Activity entries on the Person or Account timeline. We preserve the meeting title as the Activity subject and outcome notes as the Activity description. Recurring meetings from Barantum are expanded into individual Activity records, one per occurrence, with a custom field recurring_parent__c linking instances.

Barantum Lead records map to Nutshell Lead. Lead source, status, score, and custom properties migrate directly. Barantum lead-to-contact conversion history is not transferable as a conversion event in Nutshell; instead, we migrate the lead record as-is and the customer's sales team performs any necessary lead qualification in Nutshell manually or via a rebuild workflow.

Barantum Activity logs tied to contacts or deals migrate to Nutshell Activity records. Activity type (call, note, task) is preserved via a custom activity_type__c field. Barantum's custom activity types configured by the customer are enumerated during discovery and mapped to Nutshell Activity types or stored as a custom text field. Activity timestamps and owner attribution migrate directly.

Barantum User and Agent accounts (name, email, role, extension) are exported for owner/agent mapping in Nutshell. We resolve Barantum agent IDs to Nutshell User records by email match. Barantum's agent extension and role fields are stored as custom fields on the mapped Nutshell User record. Nutshell user seats are not created during migration; the customer's admin provisions Nutshell users based on the exported roster.