Migrate from Barantum CRM to Twenty CRM

Barantum Contact records (name, phone, email, profile details, WhatsApp profile linkage) map directly to Twenty People. WhatsApp profile linkage is preserved as a custom field rather than a native reference, since Twenty does not have native WhatsApp integration. The WhatsApp profile URL or phone identifier migrates as a custom property for customer reference. We run a reconciliation check after migration comparing the total Contact count exported to the total People records created in Twenty to catch any dropped records.

Barantum Company records serve as parent entities grouping related Contacts. We migrate companies first so that when People records import, we can resolve the organization relationship using Barantum's company name as the match key. Twenty's Organization object accepts domain, industry, and address fields that map from Barantum company properties. Parent-company hierarchies map as Organization self-lookups if the source Barantum data includes them.

Barantum Deal records (stage, value, owner, expected close date) map to Twenty Opportunity. Pipeline stages in Barantum are enumerated during discovery and mapped to Twenty Opportunity stage values via a configuration table. We apply the same stage probability percentages from Barantum to Twenty OpportunityStage entries if the customer has configured them. Deal currency fields are preserved as-is; multi-currency deals require a pre-migration currency configuration in Twenty.

Barantum Leads (captured via forms, imports, or chatbot) migrate to Twenty People with a lead_source custom property carrying the Barantum lead source value and a status custom property mapping the Barantum lead status. We enumerate all Barantum lead status values during discovery and configure matching picklist options in Twenty before migration begins.

Barantum Ticket records (issue description, status, assigned agent, conversation history) map to Twenty Comment records linked to the relevant Person or Opportunity, or to a custom Case object if the customer prefers a separate support-queue schema. Ticket status values map to a Twenty picklist. Conversation history from ticket threads migrates as multiple Comment entries ordered by timestamp to preserve the support thread sequence.

Barantum Meeting records (title, scheduled time, attendees, outcome notes) map to Twenty Task records with a meeting-type custom label or type field. We preserve the original scheduled timestamp in the Task due date and add meeting attendees as a comma-separated custom field. Recurring meeting patterns in Barantum are documented as a list of individual instances rather than a recurring rule since Twenty does not support native recurring meeting templates.

Barantum Activity logs (call logs, notes, task completions tied to Contacts or Deals) map to Twenty Task records. Barantum activity types vary by configuration, so we enumerate all available activity types during discovery and map each to a Twenty Task with a type custom field. Activity timestamps become Task due dates to preserve timeline ordering. Any task completions or call outcomes migrate as Task status values.

WhatsApp and omnichannel chat histories from Barantum are extracted as separate records and migrated as Note objects linked to the corresponding Twenty Person via ContentDocumentLink. Each conversation thread becomes one Note with the full chat transcript as body text, timestamp, and agent attribution preserved as custom fields. Media file URLs migrate as a text property pointing to downloadable files; inline media does not transfer. Post-migration we reconcile Contact count to Note count to flag any conversation threads without a matching Person record.

Barantum User and agent accounts (name, email, role, extension) migrate as User records in Twenty for owner and assignee mapping. We resolve by email match. Any Barantum User without a matching Twenty User goes to a reconciliation queue for the customer admin to provision before record import resumes. New User seats are not automatically created; the customer controls which agents become active Twenty users.

Barantum custom fields added to Contacts, Companies, Deals, Tickets, or other objects are enumerated during discovery. We export all custom field values and map them to Twenty custom fields of matching data type, creating any missing fields in Twenty Settings Data Model before import. Text fields, number fields, date fields, and picklist options all transfer directly with type verification to prevent import errors from mismatched data types.