Migrate from BoomTown to Twenty CRM

BoomTown contacts map 1:1 to Twenty's People object. Every contact must link to a Company record (companyId foreign key) — contacts without a primary company receive a default 'Unassigned' company record created during migration so the relation is valid in Twenty.

BoomTown companies map directly to Twenty's Companies object. Parent-child company hierarchies and subsidiary relationships are preserved via Twenty's self-referential companyId relation field. It is critical that Companies import before People so that the companyId foreign key lookup resolves correctly when contacts are created during migration. Any orphaned company references are flagged and resolved before the People batch begins.

BoomTown deals map to Twenty's Opportunities object. Each deal's stage name maps to a Twenty opportunity stage pick-list value — if BoomTown uses custom stage names, value-by-value mapping is required before import. Close dates, amounts, and owners carry over as-is.

BoomTown pipeline stage names are pick-list values that require explicit value mapping to Twenty's opportunityStage field. Stage order and probability weights are re-applied in Twenty after mapping. HubSpot-style multi-pipeline setups collapse to one Twenty pipeline unless custom fields are used to simulate pipeline branching.

BoomTown owner IDs resolve to Twenty WorkspaceMembers by email match. All Twenty users must accept their invite before import — otherwise owner assignments fail and records land with an unassigned owner. We flag unmatched owners before migration and let you assign a fallback owner.

BoomTown call logs, email records, meetings, and notes migrate as Twenty Tasks and Notes. Tasks inherit the original timestamp and the owner who created the activity in BoomTown. The activity type (call, email, meeting) is stored as a custom select field on the Task for filtering.

BoomTown drip campaigns and sequences have no native equivalent in Twenty's current workflow builder. We export the drip campaign definitions (stage triggers, delay days, content) as a structured JSON reference file. Rebuild in Twenty's workflow builder or an external sequencing tool using this file as a specification.

BoomTown lead assignment rules (geo-routing, round-robin, team-based) do not have a direct mapping. We export the rule logic as a configuration document. Twenty's workflow automations can replicate assignment logic — your admin rebuilds these using Twenty's Conditions and Actions with guidance from the exported rules.

BoomTown real estate custom objects (listings, transactions) map to Twenty custom objects created during migration planning. BoomTown N:N relationships between custom objects require a junction custom object in Twenty to maintain the association structure. We document the required schema before creating the custom object in Twenty.

BoomTown's IDX website data and property listings are real estate-specific objects without a Twenty equivalent. We migrate listing data as a custom object with fields for address, MLS ID, status, and price. Property images re-upload as file attachments linked to the listing record.

BoomTown's predictive lead scoring (behavioral activity-based) migrates as a custom Number field on the Person object. The scoring algorithm itself — which is BoomTown-proprietary — does not replicate; only the last-known score value transfers as a static number for reference.

BoomTown transaction records including deal-related contracts and e-signatures migrate as a Twenty custom object linked to the relevant Opportunity via a custom relation field. Transaction status, involved parties, key dates (execution, closing, expiration), and monetary values become custom fields on the custom object. E-signature documents and supporting contract files re-upload as file attachments on the transaction record after migration.