Migrate from Salesboom to Microsoft Dynamics 365 Sales

Salesboom Accounts map directly to Microsoft Dynamics 365 Account. We preserve the full Account hierarchy, billing and shipping addresses, industry classification, and any custom Account fields. Salesboom's Account website field maps to the Account Website field in Dataverse. In Dynamics 365, Account is the primary company-level record and is created before any Contact import so that the AccountId lookup is satisfied at Contact insert time.

Salesboom Contacts attach to Accounts and map to Dynamics 365 Contact with a required AccountId lookup. We resolve the AccountId at migration time using email domain or company name matching against the already-migrated Account records. Custom Contact fields on Salesboom are recreated as Dataverse columns and populated during import. Dynamics 365 enforces the Contact-Account relationship at the validation level, unlike Salesboom where Contacts can exist without an explicit parent Account.

Salesboom Leads map to Dynamics 365 Lead. The Lead object in both platforms stores prospect-level information independently of Accounts and Contacts. We preserve lead status, rating, source, and any custom lead fields. Dynamics 365 Lead uses LeadToOpportunityFlow for conversion, which we document but do not configure as part of migration scope. The original Salesboom lead creation date migrates as CreatedOn in Dataverse.

Salesboom Opportunities map to Dynamics 365 Opportunity. Stage names, amounts, close dates, probabilities, and descriptions migrate directly. We configure the Microsoft Dynamics 365 Sales Process to whitelist the migrated stage values so that imported Opportunities are valid against the destination org's validation rules. Opportunity-Account lookups are resolved after Account migration is complete. Custom Opportunity fields are recreated as Dataverse columns.

Each Salesboom Opportunity stage value becomes a Dynamics 365 StageName entry in a Sales Process that we configure in the target environment before Opportunity migration begins. We set StageProbability values to match the source percentages and map CloseReason from Salesboom's closed-lost or closed-won disposition field. If Salesboom uses multiple pipelines, each becomes a separate Record Type in Dynamics 365.

Salesboom Tasks map to Dynamics 365 Task. Subject, Status, Priority, Due Date, and Description migrate. In Dynamics 365, Tasks appear on the unified activity timeline alongside Events. We set the Regarding (object) lookup by resolving the parent AccountId or ContactId from the original Salesboom association. Task.Subject and Task.ActivityDate preserve the original Salesboom timestamps for timeline ordering.

Salesboom Calendar Events map to Dynamics 365 Event. Start time, end time, location, and body text migrate. We create EventRelation records for each attendee, resolving the attendee against migrated Contact and User records by email. Event records appear on the Dynamics 365 activity timeline in chronological order using the original Salesboom event timestamps. All-day events are flagged using the IsAllDayEvent field.

Salesboom Notes attach to any parent record (Account, Contact, Opportunity) and map to Dynamics 365 Note. Note title, body text, created date, and owner migrate. Rich-text formatting in Salesboom Notes is preserved as plain text to ensure compatibility with the Dataverse Note schema. Notes appear in the Dynamics 365 timeline view of the relevant record.

Salesboom Cases map to Dynamics 365 Case if the destination org includes the Customer Service app. Case status, priority, origin, subject, and description migrate. Dynamics 365 Case uses a different status model (Active, Resolved, Cancelled with sub-statuses) that we configure before import to accept the migrated status values. Auto-assignment rules and escalation workflows do not migrate; we document them in the automation inventory for the customer's admin to rebuild in Dynamics 365 Case Management.

Salesboom custom fields on any standard tab (Lead, Account, Contact, Opportunity, Case) are recreated as Dataverse custom columns in the Dynamics 365 target environment. There is no shared field ID space between the two platforms, so each custom field requires explicit schema provisioning. We capture the Salesboom field type and map it to the nearest Dataverse column type (Text, Integer, Decimal, Boolean, DateTime, or Option Set). Custom field data is migrated after the destination schema is deployed and validated.