Migrate from Barantum CRM to Microsoft Dynamics 365 Sales

Barantum stores all people records as Contacts with status fields for lead qualification. Microsoft Dynamics 365 Sales requires a Lead for unqualified prospects and a Contact for qualified people tied to an Account. We design the split rule during scoping using Barantum's contact status and source fields, create Leads for unqualified records, and create Contacts for qualified records with AccountId lookup resolved by company name matching. The original Barantum contact status migrates as a custom field barantum_status__c on both Lead and Contact for audit and reporting continuity.

Barantum Company records map directly to Dynamics 365 Account. Company name is the dedupe key. We migrate Accounts first so that Contact and Lead imports can resolve the AccountId lookup relationship at insert time. Barantum company-contact relationships (which contact belongs to which company) map to Account-Contact lookups via company name matching or explicit relationship fields in Barantum.

Barantum Deals map to Dynamics 365 Opportunities. Deal stage maps to Opportunity StageName; pipeline assignment maps to a Microsoft Dynamics 365 Sales Process and Record Type that we configure before migration. Deal value, expected close date, owner, and notes migrate directly. Closed-won and closed-lost reasons in Barantum custom fields map to Opportunity's closedate and stage history.

Each Barantum pipeline stage becomes a Dynamics 365 StageName value within a Sales Process. We configure the Sales Process in the destination Dynamics 365 org during schema design, mapping Barantum stage order, probability percentages, and stage names to the Dynamics 365 stage matrix. The Sales Process is validated in a Sandbox before production migration.

Barantum Tickets migrate to Dynamics 365 Cases if the destination org includes Service Cloud or Dynamics 365 Customer Service. Ticket status maps to Case Status; ticket priority maps to Case Priority. Agent assignments map to Case Owner. Chat transcript history linked to tickets migrates as EmailMessage or Note records linked to the Case.

Barantum links WhatsApp conversation threads directly to Contact records with conversation text stored as part of the contact profile. Dynamics 365 does not have a WhatsApp conversation object. We extract each conversation thread as a separate activity record: outbound messages become Task records (TaskSubtype=Task for WhatsApp-type entries); inbound messages become EmailMessage records; full transcripts become Note records with ContentDocumentLink to the parent Contact or Lead. We run a contact-count-to-conversation-count reconciliation check after migration to catch orphaned threads.

Barantum VoIP call center logs (direction, duration, agent extension, recording URL, disposition) map to Dynamics 365 Task records with TaskSubtype = Call. Call duration, disposition, and recording URL migrate to custom Task fields. We download call recordings as audio files and attach them as ContentDocument records linked via ContentDocumentLink to the parent Contact, Lead, or Opportunity.

Barantum Meetings map to Dynamics 365 Event records. Start time, end time, title, location, and attendee list migrate directly. Attendees map to EventRelation records pointing at the related Leads, Contacts, and Users. Outcome notes migrate to the Event Description field.

Barantum Activity logs (notes, task completions, call outcomes not from the call center) map to Dynamics 365 Task records. Status, Priority, and ActivityDate preserve from Barantum. Owner assignment resolves via email matching to Dynamics 365 User records.

Barantum User and Agent accounts (name, email, role, extension) export for owner mapping. We resolve Barantum agent IDs to Dynamics 365 User records by email match. Agents without a matching Dynamics 365 User go to a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId is required on most standard entities.