Migrate from Contact Beacon to Twenty CRM

Beacon Contacts map to Twenty Persons. Standard fields (name, email, phone, address) migrate directly. Owner assignment resolves via email match against Twenty Users. Beacon's custom fields on Contacts map to custom fields on the Person object created via the /metadata API. We flag any multi-select custom fields because Twenty's custom field types have different picklist behaviors that may require restructuring.

Beacon Donations map to Twenty Opportunities. The donation amount becomes the Opportunity amount, donation date becomes the close date, and the campaign tag becomes a custom Opportunity field linked to the Campaign object. Gift Aid boolean (true/false) transforms into a Gift Aid custom field with the claimed amount carried in a separate Gift_Aid_Amount__c custom field. We preserve the parent Contact relationship by linking the Opportunity to the corresponding Person record via the Twenty Person ID resolved at migration time.

Beacon Campaigns map to a Twenty custom object (Campaign__c) created at migration time via the metadata API. We create fields for campaign name, status (active/closed/paused), start date, and end date. Beacon campaign-linked donations reference this custom object via a lookup field on the Opportunity (donation). If Twenty's native workspace-level tracking is preferred, we configure opportunities with a campaign tag field at scoping based on the customer's reporting hierarchy.

Beacon Pipelines (donor journey stages) map to Twenty Opportunity stages. Stage names and order migrate as stage picklist values. Any conditional stage-routing logic from Beacon Pipelines (e.g. auto-advance based on donation amount) cannot migrate as automation and must be manually reconfigured in Twenty after migration.

Beacon tags on Contacts and Donations migrate as flat label arrays into Twenty's tagging system. We flag any tags that correspond to inactive Beacon workflows, since the workflow reference is lost and the tag meaning may need clarification during post-migration data review.

Beacon custom fields on Contacts and Donations are discovered at scoping. We create matching custom fields in Twenty via the /metadata API, mapping Beacon field types to Twenty field types. Multi-select picklists in Beacon map to multi-select in Twenty where supported; free-text fields map to text fields. Any unsupported field types are flagged for the customer's admin to review before migration.

Beacon file attachments on Contact records are downloaded via individual API requests (one per attachment) and re-uploaded to Twenty as linked files. Large attachment batches are chunked to stay within Beacon's rate limits. Twenty does not support file import via CSV, so all attachments require the API pass rather than bulk loading. Files exceeding Twenty's size limits are flagged for manual re-upload.

Beacon user accounts map to Twenty Users. We resolve by email match. Inactive Beacon users are imported as inactive Twenty Users or archived depending on the customer's preference. Owner assignment on migrated records uses the resolved Twenty User ID.

Beacon automated workflows (Gift Aid submission triggers, thank-you email sequences, donor follow-up timers) are not accessible via the Beacon API or UI export and cannot be migrated. We run a workflow audit during scoping and deliver a written inventory of every active workflow with its trigger conditions, actions, and timing logic. The customer's admin rebuilds these in Twenty or a dedicated automation tool post-migration. Gift Aid submission workflows in particular require a separate UK HMRC-compatible tool rather than generic CRM automation.

Beacon stores Gift Aid eligibility as a boolean toggle on the Contact record. We map this to a Gift Aid Declaration custom field on the Twenty Person object and carry the declaration date and HMRC claim status in separate custom fields. The Gift Aid amount claimed historically migrates as a monetary custom field on the Person for reporting purposes. HMRC Gift Aid submission itself requires a dedicated tool outside Twenty's standard automation capabilities.