Migrate from Barantum CRM to monday CRM

Barantum Contact records map to Monday.com CRM Items on a Contacts Board. Standard fields (name, phone, email, address) map to Text, Phone, Email, and Location columns. WhatsApp profile linkage stored as a custom text field referencing the external WhatsApp Business API account. Contacts are migrated first because Deal and Ticket Items reference them as connected Items via the Relations column. Any Contact records without an email receive a generated placeholder email for import compatibility.

Barantum Company records map to Monday.com CRM Items on a separate Companies Board. Contact-Company relationships migrate as Relation links (Contacts linked to their parent Company Item). For simpler setups, Company name also stores as a Text column on the Contacts Board, but a dedicated Companies Board preserves the hierarchical relationship and supports multiple contacts per company. We enumerate all Barantum Company records during discovery and the customer decides on the one-Board versus two-Board architecture.

Barantum Deals map to Monday.com CRM Items on a Sales Pipeline Board. The Barantum pipeline stage maps to the Status column; Deal value maps to a Numbers column; expected close date maps to a Date column; owner maps to a Person column. We extract every distinct Barantum pipeline and stage name during discovery and configure a corresponding Monday.com Board with matching Status values before migration. Multi-pipeline setups in Barantum map to separate Boards in Monday.com, or to separate Groups within one Board if the customer prefers a consolidated view.

Barantum Lead records (captured via forms, imports, or chatbot) map to Monday.com CRM Items on a Leads Board. Lead source, lead status, and lead score fields from Barantum map to Text, Status, and Numbers columns in Monday.com. We create a Status column with values matching Barantum's lead lifecycle stages so that conversion status is preserved. Leads that are converted to Contacts in Barantum are migrated as Contact Items with a converted-flag column rather than as Lead Items.

Barantum Tickets map to Monday.com CRM Items on a Support Board. Ticket status maps to the Status column, assigned agent maps to a Person column, and issue description maps to a Long Text column. Linked chat transcripts from Barantum export as separate Items on the same Support Board linked via the Relations column, or as PDF attachments on the Ticket Item. Agent assignment history migrates as a text log entry rather than a native audit trail.

Barantum Meeting records map to Monday.com Items on an Activities or Calendar Board. Meeting title, scheduled time, attendees, and outcome notes map to Text, Date, Person (multi-select for attendees), and Long Text columns respectively. Recurring meetings from Barantum are migrated as individual Items with a recurrence-identifier text field; the recurrence pattern is documented in the notes field for manual reconstruction in Monday.com's Calendar integration.

Barantum VoIP call records (direction, duration, agent extension, recording links) map to Monday.com Items on an Activities Board. Call duration maps to a Numbers column, direction to a Status or Labels column, and recording URL to a Link column. Call disposition from Barantum maps to a Labels column. Call recording audio files are downloaded and attached as file Items linked to the parent contact or deal via the Relations column.

Barantum Notes tied to contacts, companies, or deals map to Monday.com Items on an Activities Board linked via the Relations column to the relevant Contact or Deal Item. Rich-text notes are preserved as Long Text columns with HTML formatting stripped to plain text. Notes attached to multiple records are duplicated as separate Items with each parent linked.

Barantum WhatsApp conversation threads are embedded on Contact profiles and must be extracted as standalone Items on a Conversations Board or as PDF/text file attachments on the Contact Item. Each conversation gets its own Item with the contact name as a Relation, the conversation timestamp, and the full text thread stored in a Long Text column. Media files (images, documents) are exported as separate file attachments. This is the highest-effort object in the migration because Barantum stores conversation text as structured thread objects that must be denormalized into one Item per conversation per contact. We run a contact-count-to-conversation-count reconciliation after migration to confirm no threads are orphaned.

Barantum User and Agent accounts (name, email, role, extension) do not create new seats in Monday.com CRM. Instead, we map Barantum owner IDs and agent IDs to Monday.com User email addresses via a lookup table built during discovery. Any Barantum user without a matching Monday.com account is flagged in a reconciliation worksheet for the customer to provision before migration continues. Role and extension information migrates as Text columns on the user profile or as a separate Team Board.

Barantum custom fields on any object are enumerated during discovery and mapped to Monday.com custom columns of the nearest matching type: text fields to Text columns, numeric fields to Numbers columns, date fields to Date columns, dropdown fields to Labels or Status columns, and boolean fields to Checkbox columns. Multi-select custom fields in Barantum map to Labels columns with multiple selections. Any custom field with no Monday.com equivalent is documented in a custom field inventory with the customer's chosen fallback approach (Text column or external reference).