Migrate from EF Enterprise to Odoo ERP

EF Enterprise Exhibitions (event name, dates, venue, status) map directly to Odoo event.event records. We extract Exhibition fields from Salesforce including Exhibition__c.Name, Date__c, Venue__c, and Status__c and map them to event.event name, date_begin, date_end, address_id, and stage. Venue details migrate as address contacts (res.partner with type=contact) linked to the event.

EF Enterprise Booths are child records of Exhibition, storing booth number, size, zone, and per-booth pricing. Odoo event.booth model stores booth name, capacity, and event_id reference. We preserve the Exhibition parent via event_id lookup resolution at migration time. Per-booth pricing migrates to a custom decimal field booth_price__c on event.booth since the standard Odoo event.booth model does not include pricing.

EF Enterprise Sponsors link to Exhibitions and optionally to specific Booths, with sponsor tier flags (Gold, Silver, Bronze). We split this into two Odoo records: res.partner for the sponsor company contact (with a custom partner_tag__c for tier classification) and event.sponsor linking that partner to the event.event record with the appropriate sponsorship level.

EF Enterprise Attendee Registrations store contact reference, session selections, and badge type. We map these to Odoo event.registration with partner_id resolved from the contact reference, and badge type stored in a custom field registration_badge_type__c. Session selections require resolution to Odoo event.track records if the destination uses the Odoo Event Tracks app.

EF Enterprise Sessions carry capacity limits and track classifications linked to Exhibitions. Odoo event.track stores track name, description, date, and seat availability (seats_max, seats_available). Multi-track sessions in EF Enterprise flatten into individual event.track records per session slot with a custom field session_track_class__c carrying the original track classification.

EF Enterprise Badge Records encode attendee type, access levels, and printing status. Odoo's event.badge model stores badge information linked to event.registration. We migrate badge type as a custom field on event.badge and preserve printing status in a custom badge_printed__c boolean. Auto-print triggers from Salesforce Flow or Apex do not migrate; we document the trigger logic in a written handoff document for the customer's Odoo developer.

EF Enterprise custom objects for exhibitor contracts, floor plans, and lead retrieval are not reliably discoverable via the standard Salesforce API without customer-provided schema access. We request a Salesforce schema export during discovery and pre-create equivalent Odoo models via res.config.settings or a data migration script. If schema access is unavailable, we flag the custom object as unsupported and migrate only standard fields.

EF Enterprise stores OwnerId on records as a Salesforce User reference. We resolve owners by email match against Odoo res.users. Any EF Enterprise Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Archived Salesforce users map to Odoo users with active=False.

EF Enterprise Attachments linked to booths, sponsors, and exhibitions migrate as Odoo ir.attachment records linked to the corresponding res.model record (event.event, event.booth, res.partner). Large floor plan PDFs are chunked and re-uploaded via Odoo's ir.attachment create endpoint. ContentDocument links from Salesforce become Odoo res.model and res_id references.

EF Enterprise uses Salesforce standard tags and custom property sets for exhibitor classification. We export the full tag taxonomy and recreate it in Odoo as res.partner.category records (for sponsor/attendee tags) and ir.filters (for saved view filters on event.event and event.registration). Duplicate tags are merged during the transformation step.