Migrate from Contact Beacon to Freshsales

Contact Beacon Contacts map directly to Freshsales Contacts. Standard fields (name, email, phone, address) transfer one-to-one. The Contact record is the primary anchor object in Freshsales, so it is imported before any related records to satisfy lookup dependencies. Owner assignment maps from Beacon user ID to Freshsales User via email match.

Beacon Donation records map to Freshsales Deals. The donation amount maps to Deal Amount, the donation date maps to Expected Close Date, and the associated Campaign tag maps to a custom Deal field (e.g. fundraising_campaign__c). The Gift Aid boolean flag maps to a custom checkbox field (gift_aid_eligible__c) that we create in Freshsales during schema design. Parent Contact relationship is resolved at migration time to populate Deal Contact Name.

Beacon Campaigns are lightweight grouping objects used for donation attribution. Freshsales has no native Campaign object equivalent to Beacon's fundraising campaigns. We map campaign names to a custom multi-select or text field on the Deal object so that fundraising attribution is preserved per donation. If the customer has more than 20 campaigns, we recommend a separate Freshsales List or Tag structure instead.

Beacon per-organization custom fields on Contacts and Donations are discovered at scoping. We map Beacon field types to Freshsales field types: text to text, number to number, date to date, checkbox to checkbox. Multi-select picklist fields from Beacon map to Freshsales multi-select picklist if the destination plan supports it, otherwise to a text field with a documented value list.

Beacon Pipelines track donor journeys and fundraising stages as separate workflow tracks. Freshsales has a single pipeline model with configurable deal stages. We map Beacon pipeline stage names to Freshsales deal stage values and configure the stage order in Freshsales Admin before migration. Conditional stage-routing rules in Beacon cannot be transferred and must be reimplemented as Freshsales workflow rules post-migration.

Beacon automated workflows (Gift Aid submission triggers, thank-you email sequences, donor follow-up timers) have no export path via API or UI. We do not migrate workflows as code. During scoping we run a workflow audit and produce a written inventory documenting every active automation with its trigger, conditions, actions, and recommended Freshsales workflow equivalent. The customer or a Freshworks partner rebuilds each workflow post-migration.

Tags on Beacon Contacts and Donations migrate as flat label arrays to Freshsales Tags. Tags that correspond to inactive Beacon workflows are flagged in the migration documentation so the customer can decide whether to recreate them in Freshsales or retire them. Tag counts are preserved in a custom field for reporting purposes.

File attachments on Beacon Contact records are downloaded via individual API requests and re-uploaded to the corresponding Freshsales Contact record. Large attachment batches are chunked to stay within Beacon's rate limits. We cannot process attachments in bulk parallel due to per-key rate constraints; the re-upload uses Freshsales' attachment API endpoint.