Migrate from Barantum CRM to HubSpot

Barantum stores both leads and contacts in a single contacts object with a status field. We map every Barantum contact record to a HubSpot Contact. Barantum's lead status values map to HubSpot's lifecycle_stage property via a value-mapping table — your team chooses which Barantum statuses correspond to Subscriber, Lead, MQL, SQL, and Customer in HubSpot's lifecycle model.

Barantum company records map 1:1 to HubSpot Companies. Barantum's company domain field maps to HubSpot's domain property. Barantum's parent-company hierarchy (if configured) maps to HubSpot's parent company association using HubSpot's parent_company_id field. Companies are migrated before contacts so that contact-to-company associations resolve correctly via HubSpot's association model.

Barantum deals map to HubSpot Deals with the deal name becoming the dealname, amount carrying over directly, and closedate mapping to HubSpot's closedate field. Barantum deal stage names map to HubSpot deal pipeline stage names via value mapping — we deliver the mapping table in the migration plan so your team can verify that Barantum stages align with the HubSpot pipeline stages you have configured.

Barantum ticket records map to HubSpot Tickets. The ticket subject maps to the ticket name, and ticket status maps to HubSpot's ticket pipeline stage. Barantum's ticket priority and category fields migrate as custom properties on the HubSpot Ticket object since HubSpot's default ticket schema uses a single pipeline stage model.

Barantum meeting records map to HubSpot Meetings with the original start time, end time, title, and organizer preserved. The meeting is associated to the relevant HubSpot Contact, Company, or Deal record via HubSpot's association API. Barantum meeting descriptions migrate as meeting notes attached to the HubSpot Meeting record.

Barantum call logs — including call direction, duration, outcome, and recording reference — migrate as HubSpot Call engagements on the relevant Contact or Deal timeline. The call recording URL is stored as a custom property on the Call record since HubSpot's native call logging does not support inline recording attachments without a connected telephony integration.

Barantum chat and WhatsApp conversation history migrates as HubSpot Timeline Notes on the associated Contact or Company record. Each message is represented as a timestamped note entry with the message text, sender, and channel (chat or WhatsApp) preserved. This preserves the relationship history without requiring a native WhatsApp integration in HubSpot — teams can reconnect WhatsApp via HubSpot's Conversations Inbox post-migration.

Barantum tasks map to HubSpot Tasks with subject, due date, priority, and completion status preserved. Open Barantum tasks migrate as open HubSpot Tasks assigned to the same owner (resolved by email match against HubSpot users). Completed tasks migrate with their completion timestamp recorded in the task's completion date field.

Every Barantum custom field on contacts, companies, deals, and tickets is created as a HubSpot custom property before the migration runs. Property types are mapped: Barantum text fields become HubSpot single-line text or multiple-line text properties; pick-list fields become HubSpot select or radio selection properties with the same options; number fields map to HubSpot number properties; date fields map to HubSpot date-picker properties. We surface the complete property creation list in the migration plan so your HubSpot admin can pre-create properties or approve the mapping before data loads.

Barantum owner IDs are resolved by email address against HubSpot users. Any Barantum owner without a matching HubSpot user email is flagged before migration — your team either creates the HubSpot user account or assigns those records to a fallback HubSpot owner. Records do not land without a resolved owner to maintain data integrity in HubSpot's assignment model.

Barantum workflow rules, automation sequences, and autoresponder logic do not migrate. These are platform-native business logic that requires rebuilding inside HubSpot's Workflows tool (Sales Hub Professional+ or Service Hub). We export your Barantum workflow definitions — triggers, conditions, and actions — as a structured JSON reference document that your HubSpot admin can use to rebuild equivalent automation in HubSpot's workflow builder.