Migrate from Contact Beacon to Odoo CRM

Beacon Contacts migrate to Odoo Contacts with all standard fields (name, email, phone, address) and any custom per-organization fields mapped to Odoo custom Contact fields. The Beacon contact_id becomes an external identifier in Odoo for reconciliation. Owner assignment maps to the Odoo user field; inactive Beacon users are imported as Odoo inactive users or archived records based on the destination org's user management policy. Address fields are mapped field-by-field to Odoo's street, city, state, zip, country structure.

Beacon Donations are the primary structural transformation in this migration. Each Donation maps to an Odoo CRM Opportunity with the following custom field mapping: donation amount to Expected Revenue, gift date to Expected Closing, campaign tag to Tag IDs in Odoo, and the Gift Aid boolean flag to a custom boolean field gift_aid_eligible__c on the Opportunity. The parent Contact relationship is preserved by resolving the Beacon contact_id to the Odoo Contact record ID at migration time and setting the Opportunity's Partner ID to the resolved Contact. Note that Odoo has no native donation record type; the Opportunity with custom fields is the conventional Odoo model for tracking charitable gifts.

Beacon Campaigns group Donations and Contacts for reporting. Odoo CRM does not have a native Campaign object equivalent to HubSpot or Salesforce Campaign. We map Beacon Campaigns to Odoo Tags on the Opportunity (representing the donation campaign) and optionally create a separate Tag on the Contact for donor attribution. If the customer is activating Odoo Events, the Campaign can alternatively map to an Odoo Event project for event-linked fundraising tracking. The mapping strategy is chosen during scoping based on the customer's reporting requirements.

Beacon Pipelines with ordered Stages map to Odoo CRM Stages within the default pipeline. Stage names and order are migrated; probability percentages per stage are set on each Odoo Stage configuration. Any conditional stage-routing rules from Beacon (e.g., automated stage advancement based on donation amount) cannot migrate as automation and are documented as Odoo CRM Server Actions for the customer's admin to configure post-migration. Odoo's default pipeline is single; if the customer needs multiple pipelines, we configure additional CRM Sales Teams as pipeline partitions during the schema design phase.

Beacon per-organization custom fields on Contacts and Donations are discovered during scoping and mapped to Odoo custom fields on the Contact and Opportunity respectively. Field types are translated: text to char, number to float or integer, date to date, checkbox to boolean, multi-select to many2many tags. Unsupported types (e.g., Beacon-specific formatted fields) are flagged for manual review and either mapped to char or excluded with a documented rationale. Custom field naming in Odoo follows the field_ naming convention and must be confirmed with the customer admin before schema deployment.

Beacon Tags on Contacts and Donations migrate as Odoo Tags. Tags are stored as a many2many field on both Contact and Opportunity in Odoo CRM. We flatten Beacon's tag arrays and upsert them into Odoo's tag table, then link them to the corresponding records during import. Any tags that were generated by inactive Beacon workflows are flagged in the tag inventory document so the customer can decide whether to create corresponding Odoo automated actions or remove them.

File attachments on Beacon Contact records are downloaded via individual API requests and re-uploaded to Odoo as ir.attachment records linked to the Contact via a many2one res_model = res.partner relationship. Large batches are chunked to respect Beacon's rate limits. We log the original filename and attachment date for reconciliation. Attachments exceeding Odoo's default 100 MB file size limit are flagged for the customer's admin to store externally and link via URL.

Beacon user accounts map to Odoo Users. We match by email address. Any Beacon user without a matching Odoo User is held in the reconciliation queue for the customer's Odoo admin to provision before record import proceeds. Inactive Beacon users are set to inactive in Odoo to preserve owner attribution on historical records.

Beacon automated workflows (Gift Aid submission triggers, thank-you email sequences, donor follow-up timers) cannot be exported from Beacon's UI or API. We document every active workflow during scoping with its trigger, conditions, actions, and timing logic. This document is delivered to the customer as a rebuild guide for Odoo CRM Server Actions and Odoo's Email Templates for email sequences. We do not rebuild workflows inside the migration scope; this is an admin task post-migration or a separate consulting engagement.

Beacon stores Gift Aid eligibility as a boolean toggle on the Contact or Donation. In Odoo, we create two custom Opportunity fields: gift_aid_eligible__c (boolean) and gift_aid_amount__c (float) for the estimated HMRC reclaim amount based on donation amount times the 25% Gift Aid multiplier. For UK charities, this field enables Gift Aid batch reporting directly from the Odoo CRM Opportunity list view. The gift_aid_eligible__c boolean also drives Odoo automated actions for Gift Aid acknowledgment email templates if configured post-migration.

Beacon engagement notes migrate to Odoo CRM Notes attached to the Contact or Opportunity record. Notes with timestamps preserve the original date as the note creation date in Odoo. If a Beacon note references a specific donation, we link it to the corresponding migrated Opportunity using the external identifier cross-reference created during the donation import phase.

Beacon task engagements (follow-up reminders, donor check-ins) map to Odoo CRM Tasks linked to the Contact or Opportunity. Task status, priority, and due date migrate directly. Owner assignment resolves through the User mapping. Tasks are inserted after Contact and Opportunity records are confirmed in Odoo to satisfy the res_model and res_id foreign key constraints.