Migrate from BoomTown to Microsoft Dynamics 365 Sales

BoomTown Contact maps directly to Dynamics 365 Sales Contact. The primary company on the BoomTown contact populates Contact.ParentAccountId — if the contact has no company, it attaches to a placeholder 'Unassigned Account' record. Email address serves as the unique identifier for owner resolution during migration.

BoomTown Lead maps to Dynamics 365 Sales Lead. Lead source, status, and rating transfer as new_leadsource, new_status, and new_rating custom fields since Dynamics 365 Lead Status pick-list values may not match BoomTown's taxonomy. Original create timestamp preserved as new_originalcreatedate. If a lead already exists in Dynamics 365, FlitStack matches on email address and updates the existing record to avoid duplication.

BoomTown Company maps to Dynamics 365 Sales Account. Parent-child company hierarchies (BoomTown parent_company_id) translate to Account.ParentAccountId. Multi-address companies collapse to a single Account address record with additional addresses preserved as new_additionaladdress custom fields. For companies lacking a parent relationship, FlitStack links them to a placeholder account named 'Unassigned' to satisfy the ParentAccountId requirement and maintain referential integrity.

BoomTown Transaction maps to Dynamics 365 Sales Opportunity. Transaction amount, stage name, and close date map directly to Opportunity.Amount, Opportunity.StageName, and Opportunity.CloseDate. The BoomTown pipeline ID determines which Business Process Flow attaches to the Opportunity record via the ProcessId field.

BoomTown pipeline stages map to Dynamics 365 Sales Opportunity StageName values. Each BoomTown pipeline requires a corresponding Business Process Flow in Dynamics 365. Stage probability weights do not transfer automatically — FlitStack surfaces a stage-probability mapping table for your Dynamics 365 admin to configure before the full migration run.

BoomTown's behavioral lead scoring is a proprietary value with no native equivalent in Dynamics 365 Sales. FlitStack migrates the numeric score to a new_number field (new_predictivescore) on the Lead table. Dynamics 365 Sales Enterprise customers may alternatively configure Sales Insights scoring, which operates independently of the migrated value.

BoomTown engagement activities map to Dynamics 365 Sales activity records. Calls map to Task with activitytypecode='task' and new_activitytype='call'. Emails map to Email (activitypointer) with subject and description preserved. Meetings map to Appointment. Original timestamps and owner assignments carry forward via the OwnerId field.

BoomTown file attachments on leads, contacts, companies, or transactions download and re-upload to Dynamics 365 Sales as Annotation (Note) records. Files exceeding 128MB per note attachment require SharePoint document library integration — FlitStack documents this threshold in the migration plan and offers a SharePoint configuration add-on.

BoomTown user IDs resolve to Dynamics 365 Sales SystemUser records by email match. FlitStack builds an owner mapping table before migration — any BoomTown user without a matching email in your Dynamics 365 tenant is flagged for fallback owner assignment. Active/inactive status from BoomTown sets the SystemUser.IsDisabled flag in Dynamics 365.

Any BoomTown custom field not matching a standard Dynamics 365 Sales field name creates a new_customfieldname column in Dataverse. Custom fields require provisioning in the Dynamics 365 Power Apps solution before the migration run — FlitStack generates the field manifest as part of the pre-migration schema plan.

BoomTown workflows, sequences, and lead-routing automations do not migrate. They must be rebuilt in Power Automate or Dynamics 365 native workflows. FlitStack exports BoomTown workflow definitions as a JSON reference document your team uses to rebuild automations in Dynamics 365 — this is a FlitStack deliverable separate from the data migration run.

BoomTown's IDX website layer, MLS integration, and managed PPC campaigns are platform-bound and cannot migrate. These are not CRM data — they are infrastructure that must be re-platformed separately. FlitStack flags these as non-migratable in the migration plan and recommends a web development partner for IDX rebuild on your chosen CMS.