BoomTown to Salesforce migration
Moving from BoomTown to Salesforce Sales Cloud is a common path for real estate brokerages that have outgrown the platform's predictive CRM model and need Salesforce's enterprise-grade Account, Contact, and Opportunity objects with RecordTypeId-scoped page layouts. FlitStack AI maps every lead, contact, transaction, and activity from BoomTown's flat data model into Salesforce's relational schema — preserving original create dates, owner assignments, and lead-score history as custom fields on Lead and Contact records.
FlitStack AI migrates lead + contact + accounts, lead_score__cs, campaign + campaign members, opportunities and opportunity stagenames from BoomTown to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

What moves from BoomTown to Salesforce?
BoomTown structures its CRM around a flat contact-centric model: leads, drip-campaign membership, predictive scores, and transactions live in a single object space without the Account/Contact split that Salesforce enforces.
Read the full summary
When migrating to Salesforce Sales Cloud, BoomTown contacts map to both Account and Contact records, requiring the Account to exist before Contact creation and requiring a decision about primary brokerage assignment. BoomTown's predictive lead-score values become a custom Number field on the Salesforce Lead object. Drip-campaign enrollment history transfers as Campaign Member records, giving your Salesforce admin the raw material to rebuild outreach sequences in Salesforce Sales Engagement or Marketing Cloud. Transaction records map to Opportunities with the real-estate-specific StageName values preserved. We handle BoomTown's API v2 endpoints to extract full contact and activity histories, map those into Salesforce Bulk API format, and run field-level validation before committing the full dataset. Workflows, automations, and IDX website configurations do not transfer — those require Salesforce-native rebuilding using Flow, Web-to-Lead, and Experience Cloud.
Lead / Contact (combined) → Lead + Contact + Account
BoomTown does not separate person from organization — the company field on a BoomTown contact holds the brokerage name.
How it maps
FlitStack creates a Salesforce Account for each unique company value first, then creates a Contact linked via AccountId. If the BoomTown record is a pure prospect without a brokerage, it lands as a Salesforce Lead.
BoomTown Predictive Score → Lead_Score__c (custom Number field on Lead)
BoomTown's behavioral predictive score is a numeric property on each contact record with no Salesforce native equivalent.
How it maps
We create Lead_Score__c on the Lead object and populate it from BoomTown's score field. For converted contacts, we also create Contact_Score__c on the Contact object for reporting parity.
Drip Campaign Enrollment → Campaign + Campaign Member
BoomTown drip campaigns are sequences tied to lead status.
How it maps
The enrollment record — which campaign, when enrolled, current step — migrates as a Salesforce Campaign Member record. The sequence logic itself (step order, delay rules, content triggers) cannot migrate and must be rebuilt in Salesforce Sales Engagement or Flow using the exported campaign structure as a reference document.
Transaction → Opportunity
BoomTown transactions (real estate deals) map directly to Salesforce Opportunities.
How it maps
The pipeline name in BoomTown becomes a Salesforce Sales Process keyed by Opportunity RecordTypeId. Transaction stages (Prospecting, Showing, Under Contract, Closed) map value-by-value to Salesforce Opportunity StageName values defined per Record Type.
Transaction Stage → Opportunity StageName
Stage names from BoomTown transactions map to Salesforce StageName pick-list values per Opportunity Record Type.
How it maps
Each BoomTown pipeline requires a corresponding Salesforce Sales Process and Record Type so that stage pick-list values are scoped correctly and probability weights can be set per stage.
Activity: Call, Email, Note → Task + Event + Note
BoomTown call logs map to Salesforce Tasks with Task.Type='Call'.
How it maps
BoomTown email activities map to Tasks with Task.Type='Email'. BoomTown meeting records map to Salesforce Events with start/end times preserved. All original timestamps and owner assignments carry over via OwnerId email-match resolution.
- LeadLeadmerged
- BoomTown Predictive ScoreLead_Score__ctransformed
- Drip Campaign EnrollmentCampaigntransformed
- TransactionOpportunity1:1
- Transaction StageOpportunity StageNametransformed
- Activity: Call, Email, NoteTask1:1
+ 4 more in the mapping below
How BoomTown and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | BoomTown | Salesforce |
|---|---|---|
| Contact model | BoomTown uses flat contacts with company as a property field — no Account/Contact split | Salesforce separates Account (organization) from Contact (person) — requires parent-record creation first |
| Lead scoring | BoomTown predictive CRM assigns behavioral lead scores tracked as a numeric property on each contact | Salesforce has no native predictive score — FlitStack preserves the numeric score as Lead_Score__c custom field on Lead |
| Campaigns | BoomTown drip campaigns are platform-defined sequences tied to lead status changes | Salesforce Campaign + Campaign Member tracks enrollment history; rebuilding sequence logic requires Sales Engagement or Flow |
| Transactions | BoomTown transactions represent real estate deals with stages like Prospecting, Under Contract, Closed | Salesforce Opportunity StageName maps value-by-value from BoomTown transaction stages; RecordTypeId scopes page layouts per deal type |
| API limits | BoomTown API v2 exposes leads, contacts, activities; rate limits are not publicly documented at the enterprise tier | Salesforce Enterprise Edition caps at 100,000 daily API requests plus 1,000 per user license; Bulk API batches handle large migrations |
| Reporting model | BoomTown dashboards summarize lead pipeline and team performance within the integrated real-estate CRM | Salesforce Reports & Dashboards offer granular Opportunity, Lead, and Forecast reports by Record Type and Sales Process |
BoomTown to Salesforce field mapping
The 30 most-used fields of 38 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
firstnameContactFirstNameContact -
lastnameContactLastNameContact -
emailContactEmailContact -
phoneContactPhoneContact -
mobilephoneContactMobilePhoneContact
| BoomTown field | Salesforce field | Mapping | Note |
|---|---|---|---|
Contact.firstname | Contact.FirstName | direct | |
Contact.lastname | Contact.LastName | direct | |
Contact.email | Contact.Email | direct | |
Contact.phone | Contact.Phone | direct | |
Contact.mobilephone | Contact.MobilePhone | direct | |
Contact.title | Contact.Title | direct | |
Contact.company | Contact.AccountId | transformed | BoomTown company value creates an Account record first; Contact.AccountId links to the Account record. |
Contact.address | Contact.MailingStreet | direct | |
Contact.city | Contact.MailingCity | direct | |
Contact.state | Contact.MailingState | direct | |
Contact.zip | Contact.MailingPostalCode | direct | |
Contact.createdate | Contact.Original_Create_Date__c | custom_field_required | Salesforce CreatedDate reflects migration time; original BoomTown create date preserved as a custom datetime field for reporting continuity. |
Contact.hs_predictive_score | Contact.Contact_Score__c | custom_field_required | BoomTown predictive score maps to a custom Number field on Contact; Lead records use Lead_Score__c. |
Contact.boomtown_id | Contact.Source_System_ID__c | custom_field_required | BoomTown internal ID stored for delta-run de-duplication and rollback traceability. |
Lead.firstname | Lead.FirstName | direct | |
Lead.lastname | Lead.LastName | direct | |
Lead.email | Lead.Email | direct | |
Lead.phone | Lead.Phone | direct | |
Lead.company | Lead.Company | direct | |
Lead.status | Lead.Status | value_mapping | BoomTown lead status values map to Salesforce Lead Status pick-list; custom statuses require value-by-value mapping setup. |
Lead.leadsource | Lead.LeadSource | value_mapping | BoomTown lead source values mapped to Salesforce LeadSource pick-list. |
Lead.hs_predictive_score | Lead.Lead_Score__c | custom_field_required | BoomTown behavioral predictive score migrates to custom Number field; not native to Salesforce. |
Lead.boomtown_id | Lead.Source_System_ID__c | custom_field_required | BoomTown internal ID stored for delta-run de-duplication and rollback traceability. |
Transaction.name | Opportunity.Name | direct | |
Transaction.amount | Opportunity.Amount | direct | |
Transaction.stage | Opportunity.StageName | value_mapping | BoomTown stage names map to Salesforce StageName values per Opportunity RecordType; probability and forecast category re-applied. |
Transaction.pipeline | Opportunity.RecordTypeId | transformed | BoomTown pipeline becomes Salesforce Sales Process keyed by RecordTypeId; one pipeline = one Record Type. |
Transaction.closedate | Opportunity.CloseDate | direct | |
Transaction.owner_id | Opportunity.OwnerId | transformed | BoomTown owner email matched to Salesforce User; unmatched owners flagged before migration. |
Transaction.boomtown_id | Opportunity.Source_System_ID__c | custom_field_required | BoomTown transaction ID stored for delta-run de-duplication and rollback traceability. |
What to watch for in a BoomTown to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
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.
How we handle it
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.
How we handle it
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.
How we handle it
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.
How we handle it
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.
How we handle it
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.
How the migration runs
Extract BoomTown data via API v2
FlitStack connects to your BoomTown account using API v2 credentials to export all contacts, leads, transactions, campaign enrollment history, and activity records.
What this step covers
We pull full record payloads including custom properties, owner assignments, and timestamps. A pre-extract data audit flags records with missing required fields (e.g., contacts with no email address) and duplications so your team can decide on cleanup approach before migration begins.
Create Salesforce schema: Account Record Types, custom fields, and Sales Processes
Before any data loads, FlitStack delivers a Salesforce schema setup plan specifying the Record Types, Sales Processes, and custom fields needed.
What this step covers
Your Salesforce admin (or our team) creates Lead_Score__c, Contact_Score__c, Source_System_ID__c, and Original_Create_Date__c on the appropriate objects. We also specify the Account Record Types for each brokerage branch if you run multi-office configurations. This step ensures Salesforce is ready to receive BoomTown's flat data model without foreign-key violations.
Resolve BoomTown owners to Salesforce users by email
FlitStack matches BoomTown owner email addresses against your Salesforce user list.
What this step covers
Any owner who does not have a corresponding Salesforce user is flagged with a pre-migration report. Your team decides whether to invite the agent to Salesforce first or assign their records to a designated fallback user. No Opportunity, Lead, or Contact record is loaded without a resolved OwnerId to prevent Salesforce validation errors.
Sequence migration: Accounts → Contacts/Leads → Opportunities → Activities → Campaign Members
Salesforce requires a load order because of foreign-key dependencies — Accounts must exist before Contacts can link via AccountId, and Opportunities reference Contacts via OpportunityContactRoles after both exist.
What this step covers
FlitStack sequences the migration in phases: first all unique BoomTown company values create Salesforce Accounts, then BoomTown contacts become Salesforce Contacts with AccountId resolved, then pure prospects become Leads, then Opportunities are created with pipeline-to-RecordTypeId mapping and stage values set, then activity Tasks and Events are loaded, and finally Campaign Member enrollment records are attached to their parent Campaigns.
Run sample migration with field-level diff
A representative sample — typically 100–500 records spanning contacts, leads, transactions, and a few Campaign Members — is migrated first.
What this step covers
FlitStack generates a field-level diff showing source value vs. destination value for every mapped field. You verify that BoomTown lead scores landed in Lead_Score__c, that transaction stages matched Salesforce StageName values per Record Type, and that owner resolution produced no orphaned records. The diff report is reviewed before the full run commits.
Full migration with delta-pickup window and audit log
The full BoomTown dataset is migrated to Salesforce using Bulk API to handle high record volumes efficiently.
What this step covers
A delta-pickup window of 24–48 hours captures any records created or modified in BoomTown during the cutover window. Every operation — inserts, updates, skips, and errors — is logged in an audit trail. One-click rollback reverts the Salesforce org to its pre-migration state if reconciliation reveals data integrity issues that cannot be resolved in the field.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with three factors: total record count from BoomTown (contacts, leads, transactions, activities), the number of custom fields in use beyond BoomTown's standard set, and the complexity of the transaction-pipeline-to-Opportunity-StageName value mapping. BoomTown setups with more than five active drip campaigns fall into the upper range because Campaign Member enrollment history adds data volume. Custom field creation on Salesforce — including Lead_Score__c, BoomTown_Source_ID__c, and Original_Create_Date__c — is included in the base scope. Multi-office or multi-team configurations requiring separate Salesforce Record Types per brokerage branch add planning hours. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for BoomTown to Salesforce →Why teams move from BoomTown to Salesforce
- BoomTown's bundled pricing — Launch tier at roughly $1,000/month plus setup fees — becomes restrictive as teams scale beyond two users. Salesforce's per-seat Starter Suite at $25/user/month offers a lower per-agent cost for growing brokerages while unlocking Account/Contact/Opportunity relationships that BoomTown's flat model cannot represent.
- Reporting depth in BoomTown is constrained by the platform's built-in dashboards. Salesforce reporting with custom report types, joined reports across Account and Opportunity, and Tableau or Salesforce Reports & Dashboards delivers forecasting and pipeline analysis that BoomTown cannot match without third-party integrations.
- BoomTown's IDX website and lead-generation features are tightly bundled — switching away from BoomTown's managed PPC campaigns requires a separate marketing stack. Salesforce paired with a dedicated marketing automation tool (Marketing Cloud or a comparable platform) separates CRM costs from lead-generation costs, giving brokerages more control over marketing spend.
- As brokerages grow into multi-office or franchise structures, BoomTown's team management tools hit limits on territory assignment, role-based access, and page-layout customization. Salesforce's profile-based permissions, sharing rules, and Record Type per business unit handle multi-office hierarchies without requiring a separate instance.
- Acquired brokerages or those consolidating onto a single CRM post-merger often already run Salesforce. The migration from BoomTown to the existing Salesforce org is the fastest path to a unified record view across all acquired leads and transactions. This eliminates the need to maintain separate systems, reconcile duplicate records, or manually export data between platforms during the transition period.
Questions, answered
BoomTown to Salesforce migration questions
How long does a BoomTown to Salesforce Sales Cloud migration take?
Most BoomTown-to-Salesforce migrations complete within 48–72 hours of clock time for datasets under 50,000 records. Larger setups with 500,000+ records, multiple transaction pipelines, or extensive drip campaign enrollment history extend to 5–7 days. The longest planning step is Salesforce schema setup — creating Record Types and Sales Processes per BoomTown pipeline before data lands. We recommend scheduling the schema setup phase 1–2 weeks before the migration run to allow time for testing page layouts and field-level security settings on the new custom fields.
Will my BoomTown workflows and drip campaigns migrate to Salesforce Flow?
No. FlitStack migrates data and schema only — BoomTown drip campaign sequences, automated actions, and lead-routing rules do not transfer. These are platform-defined workflow objects stored in BoomTown's automation engine and cannot be exported as functional logic. We migrate campaign enrollment history (who was enrolled in which campaign and when) 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 campaign structure as a rebuild reference document.
What happens to BoomTown predictive lead scores in Salesforce?
BoomTown predictive scores are numeric behavioral values with no native Salesforce equivalent. FlitStack creates a Lead_Score__c custom Number field on the Salesforce Lead object and populates it with the exact numeric values from BoomTown at migration time. For contacts, we create Contact_Score__c. These are static values reflecting BoomTown's last calculation — they do not update automatically. If you later enable Salesforce Einstein Lead Scoring, it will generate its own scores based on Salesforce activity data.
Can I migrate BoomTown custom properties to Salesforce custom fields?
Yes. Any custom properties configured in BoomTown on contacts, transactions, or companies are extracted as part of the migration and mapped to corresponding custom fields on the Salesforce target object. Custom text fields become text fields, custom pick-lists become pick-lists, custom numbers become numbers. Field type mapping is handled automatically. We create the custom fields in Salesforce during the schema setup phase using the __c suffix naming convention.
What happens to my BoomTown IDX website and MLS integration after migration?
BoomTown's IDX websites and MLS integration settings are platform-bound configurations that cannot be exported. If you need IDX functionality after migrating to Salesforce, you must implement a separate IDX solution — IDX Broker, Realtor.com's platform, or a custom Experience Cloud implementation — that connects to Salesforce as a standalone product. The CRM data migration and the website layer are separate projects with independent timelines.
Does the migration affect my BoomTown account during cutover?
No. FlitStack uses scoped read access on BoomTown via API v2 — your team continues working in BoomTown throughout the migration. A delta-pickup window of 24–48 hours after the initial migration run captures any records created or modified in BoomTown during the cutover. At go-live, your Salesforce org reflects BoomTown's final state including all delta changes. No downtime or locking occurs on the BoomTown side.
How does FlitStack handle BoomTown contacts without a company name?
BoomTown contacts sometimes have a blank company field — an agent working a personal referral without a brokerage. In Salesforce, contacts without an AccountId are valid if the 'Contacts to accounts without accounts' setting is enabled. Alternatively, these records can land as Salesforce Leads with the Company field populated from other available data (e.g., the contact's email domain). FlitStack surfaces these records in the pre-migration data audit and lets you choose the handling rule before the migration run.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Accelo to SalesforceMapping · history · rollbackCliniko to SalesforceMapping · history · rollbackKlipy CRM to SalesforceMapping · history · rollbackVendasta to SalesforceMapping · history · rollbackOntraport to SalesforceMapping · history · rollbackAdobe Campaign to SalesforceMapping · history · rollback BoomTown to HubSpotMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from BoomTown to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote