Migrate from Contact Beacon to Pipedrive

Contact Beacon Contacts migrate to Pipedrive Person records with standard fields (name, email, phone, address) preserved directly. Custom fields on Beacon Contacts are discovered at scoping and mapped to Pipedrive custom fields of equivalent type. The Beacon owner assignment maps to Pipedrive's user_id field on the Person record. If Beacon stores a photo URL, it transfers as a custom text field rather than an inline image since Pipedrive Person records do not support a native profile photo field.

Each Contact Beacon Donation migrates as a Pipedrive Deal linked to the Person record via email-based lookup. The donation amount maps to Deal value, donation date maps to close_date, and the campaign tag becomes a Deal label or a custom field. Gift Aid eligibility (the boolean flag) is stored as a custom checkbox field gaid_eligible__c in Pipedrive. Multiple donations from the same Contact create multiple Deals, all linked to the same Person. We resolve the Person ID before Deal insert so the relationship is established at migration time, not corrected post-import.

Contact Beacon Campaigns have no direct Pipedrive equivalent since Pipedrive does not have a native Campaign object (it uses Organizations, Deals, and Activities). We create a Pipedrive Activity for each Beacon Campaign with the campaign name in the subject, start and end dates in the activity metadata, and a custom field campaign_status__c carrying the Beacon campaign status. Customers who need campaign-level reporting in Pipedrive can use the Activity as a grouping mechanism or implement a custom Campaign object via Pipedrive's developer sandbox.

Contact Beacon Pipelines (donor journey stages) map to Pipedrive Pipeline stages. We create a Pipedrive Pipeline named after the Beacon Pipeline, set the stage order to match Beacon's stage sequence, and configure probability percentages per stage. Any conditional stage-routing rules defined in Beacon Pipelines are documented in the migration workbook and must be manually reconfigured in Pipedrive's Stage Configuration UI after migration.

Beacon per-organization custom fields on Contacts are mapped to Pipedrive People custom fields. Field types are matched: text to text, number to numeric, date to date, single-select to single-select picklist. Multi-select fields from Beacon present a mapping challenge because Pipedrive People custom fields do not support multi-select by default; these are mapped to a text field storing comma-separated values or discussed with the customer during scoping for an alternative tagging strategy.

Beacon per-organization custom fields on Donations migrate to Pipedrive Deal custom fields. We pre-create the destination custom fields via the Pipedrive API before importing Deals so that all values land in typed fields rather than falling through to a generic data map. Any custom fields that reference other Beacon records (e.g., a lookup field to a Campaign) are resolved to the corresponding Pipedrive record ID at migration time.

Tags on Contact Beacon Contacts and Donations migrate to Pipedrive Labels on Person and Deal records respectively. Tags are extracted as flat string arrays and written as label associations via the Pipedrive API. Tags that correspond to inactive Beacon workflows are flagged in the migration workbook with a note that the triggering logic must be recreated in Pipedrive Workflows after migration.

File attachments on Contact Beacon Contact records are downloaded via individual API requests (one per attachment, chunked to stay within Beacon's rate limits) and re-uploaded to Pipedrive as Deal or Person files. We preserve the original filename and mime type. Large attachment batches (over 500 files) extend the extraction window and may push a migration into the longer timeline band.

Contact Beacon user accounts are mapped to Pipedrive Users by email match. Inactive Beacon users are provisioned as inactive Pipedrive Users or archived depending on the destination tier's handling. Owner assignment on Contacts and Donations resolves to a valid Pipedrive user_id. Any Beacon owner without a matching Pipedrive User goes to a reconciliation queue for the customer to provision before record import resumes.

Contact Beacon workflows including Gift Aid submission triggers, thank-you email sequences, and donor follow-up timers have no export path via API or UI. We run a workflow audit during scoping, document every active automation with its trigger, conditions, and actions, and deliver a written workflow inventory to the customer's admin for manual rebuild in Pipedrive's Workflow automation builder (available from Pipedrive Advanced tier). This document is included in the migration deliverables at no additional cost but the rebuild itself is outside migration scope.