Migrate from BoomTown to Pipedrive

BoomTown leads map 1:1 to Pipedrive leads. All standard lead fields (name, email, phone, source, status) transfer directly. BoomTown lead status values require value mapping to Pipedrive's lead status pick-list — any BoomTown status not already in Pipedrive's default list will be created as a custom status value before migration runs. The email address field serves as the primary duplicate-detection key across both platforms.

BoomTown contacts migrate to Pipedrive People. The Person object holds the contact's name, contact details, and primary organization link via org_id. BoomTown contact ownership resolves by email match to Pipedrive users — if no matching Pipedrive user exists, the record is flagged for manual owner assignment before the migration run proceeds. All phone variants (work, mobile, home) map to Pipedrive's phone and mobile fields.

BoomTown companies map to Pipedrive Organizations. Company name, domain, industry, employee count, and revenue fields map directly. Multi-address companies collapse to the primary address in Pipedrive's single address field per org — if your team relies on shipping or branch addresses, those should be captured as custom fields before migration. Industry pick-list values undergo value mapping to align with Pipedrive's standardized industry taxonomy.

BoomTown deals migrate to Pipedrive deals with full stage, value, close date, and owner preserved. Pipeline name in BoomTown maps to Pipedrive's pipeline by name, creating the pipeline if it does not already exist. Stage probability weights must be reapplied in Pipedrive manually after migration since BoomTown stores probability at the deal level while Pipedrive stores it at the stage level — FlitStack provides a probability mapping table to guide this post-migration configuration.

BoomTown call logs, emails, notes, and meetings migrate as Pipedrive Activities. Original timestamps and owners are preserved throughout the transfer. Activity type (call, email, meeting, task) maps to Pipedrive's activity type field. Note content migrates as activity notes with full text preserved. Linked deal and person associations are maintained via foreign-key resolution after the parent records exist in Pipedrive.

BoomTown's behavioral lead score migrates to a custom numeric field (Lead_Score__c equivalent) on both Lead and Person objects. This custom field must be pre-created in Pipedrive before migration runs. The scoring algorithm itself is BoomTown-proprietary and cannot transfer — teams must rebuild scoring logic using Pipedrive's automation triggers to increment the score field based on activities like emails opened, forms submitted, or deal stage changes.

BoomTown drip campaigns and sequence membership do not have a direct Pipedrive equivalent. We preserve campaign name and enrollment date as custom fields on the Lead for reference and audit trail. However, the email cadence logic and enrollment triggers must be rebuilt from scratch in Pipedrive Sequences. FlitStack provides a drip campaign export document listing every campaign name, step sequence, and timing for your Pipedrive admin to use as a rebuild guide.

BoomTown's lead routing rules (auto-assign to agents by geography, source, or score threshold) do not have a Pipedrive equivalent and cannot be exported. These require manual rebuild in Pipedrive Automations using condition-based triggers and user assignment rules. FlitStack documents every active routing rule in BoomTown with its criteria logic so your team can recreate each rule step-by-step in Pipedrive's rule builder after migration completes.

BoomTown custom fields for real estate (MLS number, listing status, property type, transaction ID, commission split) migrate as Pipedrive custom fields. Pipedrive requires these to be pre-created in the account before the migration runs — we deliver a custom-field creation plan specifying field name, type, and pick-list options. Teams should allocate 1-3 business days for Pipedrive admin to create these fields before scheduling the migration run.

BoomTown tracks lead source (PPC, MLS, referral, etc.) at the lead level. Pipedrive's native 'lead_source_id' can hold a value but BoomTown's attribution model may be more granular — we map it to a custom field to preserve the full attribution string. This ensures that detailed source data like PPC campaign names, MLS listing IDs, and referral partner codes are retained in Pipedrive for reporting and analysis.

BoomTown users resolve to Pipedrive users by email match. Unmatched owners are flagged before migration — teams either invite them to Pipedrive first or reassign records to a fallback user. Role and permission sets do not migrate since Pipedrive's permission model operates differently. Teams should review Pipedrive's visibility rules and admin settings post-migration to replicate appropriate access controls.

BoomTown file attachments on leads, contacts, and deals migrate to Pipedrive activity attachments. Files re-upload to Pipedrive's file storage during migration. Size limits apply — files over Pipedrive's per-upload limit (typically 64MB) require chunking or alternative storage. Teams with large file libraries should budget time to verify attachment integrity post-migration and consider using cloud storage links for very large files.