Migrate from BoomTown to Salesforce Sales Cloud

BoomTown's flat contact model requires Account-before-Contact sequencing in Salesforce

BoomTown stores contacts with a company property field rather than a separate Account object. Salesforce enforces that Contacts have a valid AccountId before creation (or a null AccountId with the 'Contacts to accounts without accounts' setting enabled). FlitStack extracts all unique company values from BoomTown contacts first, creates the corresponding Account records, then imports Contacts with AccountId links resolved. If a BoomTown contact has no company value, it lands as a Salesforce Lead or an Account named 'Unknown' based on your pre-migration configuration choice.

BoomTown predictive scores have no native Salesforce equivalent and require custom field creation

BoomTown's behavioral lead-score values are proprietary numeric aggregates based on activity patterns. Salesforce Sales Cloud has no built-in predictive score field — Einstein Lead Scoring is an add-on at the Unlimited edition tier ($330/user/month) and produces its own scores rather than migrating BoomTown's historical values. FlitStack creates a Lead_Score__c custom Number field on the Lead object and populates it with BoomTown's exact numeric values at migration time. If you later enable Einstein Lead Scoring, it will overwrite or supplement these values based on Salesforce's own model.

BoomTown drip campaign sequence logic cannot migrate to Salesforce Flow or Sales Engagement

BoomTown drip campaigns define step order, delay intervals, and content triggers tied to lead status changes. These are platform-specific workflow definitions stored in BoomTown's automation engine, not as data records. Salesforce Flow, Process Builder, and Sales Engagement sequences operate on different logic paradigms. FlitStack migrates the campaign membership enrollment record — which contact was enrolled in which campaign and at what date — as Salesforce Campaign Member records. Your Salesforce admin must rebuild the step sequencing logic using Salesforce Flow, High Velocity Sales, or Marketing Cloud Journey Builder, using the exported BoomTown campaign structure as a rebuild reference.

BoomTown IDX website data and MLS integration settings do not transfer to Salesforce Experience Cloud

BoomTown's IDX (Internet Data Exchange) websites with MLS property search integration are tightly coupled to the BoomTown platform. These configurations — property listing templates, MLS credential settings, and lead-capture forms — are not stored as exportable records and cannot transfer to Salesforce. If you need to preserve IDX functionality after migration, you must either continue hosting with BoomTown for the website layer while migrating CRM data to Salesforce, or implement a new IDX solution (such as Realtor.com's IDX platform, IDX Broker, or a custom Experience Cloud implementation) that integrates with Salesforce as a separate product.

BoomTown transaction pipelines require RecordTypeId and Sales Process setup before Opportunity migration

BoomTown supports multiple transaction pipelines with custom stage names per pipeline. In Salesforce, each pipeline must map to a combination of Sales Process and Record Type so that Opportunity StageName pick-list values are correctly scoped per deal type. If BoomTown has three active pipelines (e.g., Buyer Pipeline, Seller Pipeline, Rental Pipeline), your Salesforce org needs three Record Types and three Sales Processes configured before data lands. FlitStack delivers a schema setup plan that specifies the Record Types and Sales Processes required; the Salesforce admin creates these before the migration run.