Migrate from Contact Beacon to Nutshell

Contact Beacon Contacts map directly to Nutshell People records. Standard fields (first name, last name, email, phone, address) migrate to equivalent Nutshell Person fields. Custom properties on Contact migrate to Nutshell custom fields which must be pre-created before migration. Owner assignment maps to the Nutshell user field by email match. We flag any multi-select custom fields that exceed Nutshell's multi-select picklist limits and resolve them as text fields or separate tag records.

Contact Beacon Donations do not have a native Nutshell equivalent, so we create a custom Activity type (e.g. Donation) in Nutshell before migration. The donation amount, date, and campaign tag migrate as custom fields on the Activity. The Gift Aid boolean flag from Beacon maps to a custom Yes/No or checkbox field in Nutshell. The parent Contact relationship is preserved as a Person link on the Activity record. This mapping requires custom field schema creation in Nutshell during the setup phase.

Contact Beacon Campaigns (fundraising appeals or event groups) map to Nutshell Lists or Tags depending on how the customer uses them. We recommend mapping to Nutshell Lists for structured donor groups used in reporting, and to Tags for informal labels used for segmentation. Campaign name, status, and start/end dates migrate as List metadata or Tag description fields. The customer chooses the strategy during scoping.

Beacon Pipelines track donor journeys and fundraising stages (e.g. Prospect, Solicited, Cultivation, Active Gift, Committed). We map these to Nutshell deal pipeline stages, renaming stages to match the destination terminology. Conditional stage-routing rules defined in Beacon are documented as part of the workflow inventory and must be manually reconfigured in Nutshell's pipeline settings. Stage order and probability percentages are preserved where Nutshell supports them.

Contact Beacon custom fields on Contacts and Donations are discovered during scoping and mapped to Nutshell custom fields of equivalent type. Single-line text maps to Nutshell text fields, dates map to date fields, numbers map to numeric fields, and checkboxes map to yes/no fields. Multi-select picklists from Beacon may exceed Nutshell's limits; we flag these and resolve them as text fields. The Nutshell custom field schema must be created before any record migration begins.

Tags on Contact Beacon Contacts and Donations migrate as flat label arrays to Nutshell Tags. Tags that are associated with inactive Beacon workflows are flagged during scoping and documented as candidates for cleanup before migration. Active workflow-linked tags are preserved with a note that the associated automation must be rebuilt in Nutshell.

File attachments on Contact records are downloaded via individual Contact Beacon API requests and re-uploaded to Nutshell as files attached to the corresponding Person record or Activity record. Large attachment batches are chunked to stay within Beacon's rate limits. We do not migrate attachment version history; only the current file is transferred.

Contact Beacon user accounts are mapped to Nutshell user records by email address. Active Beacon users map to active Nutshell users; inactive Beacon users map to inactive or archived Nutshell users depending on the customer's preference. Any Beacon user without a matching Nutshell account goes to a reconciliation queue for the customer's admin to provision before record migration.