Migrate from Barantum CRM to HighLevel

Barantum Contact records map directly to GoHighLevel Contacts. We preserve name, phone (with Indonesian country code normalization), email, profile details, and address fields. Barantum's WhatsApp-linked profile data is separated: the contact profile fields map to GoHighLevel Contact fields, and the associated WhatsApp chat history is extracted as a separate conversation record linked to the Contact via a unique conversation thread ID.

Barantum Company records map to GoHighLevel Companies. Company-contact relationships are preserved by migrating Companies first, then resolving contact-to-company linkages by company name match or explicit company_id field. GoHighLevel Companies support multiple Contacts as children, matching Barantum's parent-company relationship model.

Barantum Deals map to GoHighLevel Opportunities. Each Deal's pipeline stage is resolved through a mapping table we create during scoping, since Barantum stages are free-form strings and GoHighLevel Opportunity stages are selected from a predefined list per pipeline. Deal value, owner, expected close date, and associated contact and company links migrate directly.

Barantum deal pipelines map to GoHighLevel Pipelines. We enumerate every Barantum pipeline and its associated stages during discovery, then configure matching GoHighLevel Pipelines with corresponding stage names. Stage order and probability values migrate where Barantum stores them; otherwise we set reasonable defaults and flag for customer confirmation.

Barantum Lead records (captured via forms or chatbot) map to GoHighLevel Leads. Lead source and status fields migrate to GoHighLevel's Lead source and status picklists. Leads that have already been converted to Contacts in Barantum carry the converted flag, and we map the resulting Contact record to the corresponding GoHighLevel Contact.

Barantum Tickets map to GoHighLevel Tasks with a custom task category tag (e.g., 'Support Ticket') if the destination GoHighLevel account does not have a separate ticket module enabled. Ticket status (open, pending, resolved, closed) maps to Task status (not done, in progress, done) with a note to the customer about the semantic difference. Agent assignment maps to Task assignedTo. Ticket conversation history migrates as linked notes or as separate conversation records if the customer enables the Conversations feature.

Barantum Meeting records (title, scheduled time, attendees, outcome notes) map to GoHighLevel Calendar Events. We preserve start and end time, location, and attendee list by creating GoHighLevel Events linked to the corresponding Contact or Opportunity record. Recurring meetings in Barantum expand to individual Event records in GoHighLevel.

Barantum Activity logs map to GoHighLevel Tasks. Call logs (direction, duration, disposition) migrate as Tasks with a 'Call' category tag. Notes attached to contacts or deals migrate as GoHighLevel Notes linked to the parent record. Barantum's activity type enumeration is captured during discovery and each type is mapped to the closest GoHighLevel Task category.

Barantum WhatsApp chat threads stored inline on Contact records are extracted as separate conversation records. Each conversation record retains the message text, timestamps, agent attribution, and media references. In GoHighLevel, conversations attach to Contacts via the Conversations inbox feature. This is the most critical mapping step because Barantum embeds chat history inside the contact object, while GoHighLevel stores it as linked conversation threads. We run a contact-count-to-conversation-count reconciliation check after migration to confirm every contact still references its conversation history.

Barantum VoIP call center logs (direction, duration, agent extension, recording links) map to GoHighLevel Call Logs linked to the associated Contact or Opportunity. Call recordings are downloaded as audio files and migrated as linked attachments to the Call Log record. Disposition codes map to GoHighLevel's call outcome tags or custom fields.

Barantum User and Agent accounts (name, email, role, extension) map to GoHighLevel Users by email match. We resolve agent extensions to GoHighLevel User phone settings where applicable. Any Barantum user without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

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 GoHighLevel Custom Fields of matching data type (text, number, date, dropdown, checkbox). GoHighLevel Custom Fields are managed under Settings > Custom Fields with an object selector. We pre-create destination custom fields before data import and flag any Barantum field types (e.g., multi-select, formula fields) that have no direct GoHighLevel equivalent.