Migrate from EF Enterprise to Dolibarr ERP

EF Enterprise Exhibitions (event name, dates, venue, status) map to Dolibarr llx_projet records. We extract the Exhibition name, start_date, end_date, and venue into Dolibarr extrafield columns on llx_projet (ef_exhibition_start, ef_exhibition_end, ef_venue) because Dolibarr's native Project fields cover only title, description, and status. Exhibition status (Draft, Active, Archived) maps to Dolibarr Project status (0=Open, 1=Closed, -1=Not started) via a status lookup table created during schema design. Exhibition is created first in the migration sequence so that its project_id (fk_projet) is available as a parent reference for Booths and Sessions.

EF Enterprise Booths (booth number, size, zone, per-booth pricing) map to Dolibarr llx_product records of type Service with extrafields for booth number, zone, and size. If the destination uses physical booth inventory tracking, we also create llx_entrepot records for venue zones and llx_product_stock entries per booth. Per-booth pricing migrates to llx_product.sellprice (for paid booths) or is flagged as Complimentary via an extrafield. Booth-Exhibition parent relationships are resolved via llx_projet.ref during migration so that each product is linked to the correct Dolibarr project as a WhatId equivalent.

EF Enterprise Sponsors (company name, tier, booth linkage) map to Dolibarr llx_societe records with extrafields for sponsor_tier (Gold, Silver, Bronze) and linked_booth_id. The sponsor's tier is stored in EF Enterprise as a custom Salesforce picklist; we recreate it as a Dolibarr extrafield picklist on llx_societe with equivalent values. Sponsors linked to specific Booths receive a llx_product reference via an extrafield column (ef_linked_booth_product) so that the booth-sponsor relationship is preserved. Sponsor contact persons (if any exist as separate Salesforce Contacts) migrate to llx_socpeople linked to the llx_societe sponsor record.

EF Enterprise Attendee Registrations (contact reference, session selections, badge type) map to Dolibarr llx_societe_contact records. The attendee's contact data (name, email, phone) is extracted from the linked Salesforce Contact and inserted as a llx_societe_contact entry. Session selections are stored as tags on the contact record using llx_categorie_contact and Dolibarr's category system, with a custom tag taxonomy built from the source session list. Badge type migrates to an extrafield ef_badge_type on llx_societe_contact. We do not migrate the custom registration-type fields and early-bird pricing flags that EF Enterprise stores as Salesforce custom fields without a schema export from the source org.

EF Enterprise Sessions (associated with Exhibitions, capacity limits, track classification) map to Dolibarr llx_projet_task records under the corresponding llx_projet Exhibition project. Multi-track sessions (sessions that run concurrently across different tracks within one exhibition) are flattened into individual llx_projet_task rows because Dolibarr's task model does not have a native track grouping concept; we add a extrafield ef_session_track to preserve the track classification. Session capacity limits migrate as task.fk_task_parent references or as an extrafield ef_capacity for informational purposes in Dolibarr's task view.

EF Enterprise Badge Records (attendee type, access levels, printing status) are stored as extrafields on the migrated llx_societe_contact records rather than as standalone Dolibarr objects, because Dolibarr does not have a native badge object. We create extrafield columns ef_badge_type, ef_access_level, and ef_print_status on llx_societe_contact and populate them from the source badge record data. Salesforce badge-print triggers that auto-generate badge print jobs on Attendee Registration insert are disabled before migration to prevent duplicate print jobs from firing during the batch load.

EF Enterprise Owner records (Salesforce Users assigned to Exhibitions, Booths, and Sponsors) are mapped to Dolibarr User accounts (llx_user). We resolve by email match. Any EF Enterprise Owner without a matching Dolibarr User is held in a reconciliation queue and the customer's Dolibarr admin provisions the corresponding user before the migration resumes. Inactive Salesforce Users (archived) are flagged for reassignment review during discovery rather than migrated as active Dolibarr users.

EF Enterprise Attachments linked to Exhibitions, Booths, and Sponsors (typically exhibitor contract PDFs, floor plan images, sponsor logos) are exported from Salesforce ContentDocument via the Salesforce API and uploaded into Dolibarr's documents directory tree (documents/ef_migration/{object_type}/{record_id}/). We preserve the original filename and file type. Dolibarr's ECM module (Menu Home - Documents) indexes the migrated files and links them to the corresponding Dolibarr records via llx_ecm_files entries.

EF Enterprise uses a mix of Salesforce standard tags and custom property sets for exhibitor classification. We export the full tag taxonomy (exhibitor type, booth classification, sponsor category, session track, attendee type) and recreate it in Dolibarr as llx_categorie records under the appropriate category types (Category, Contact, Product, Project). Duplicate tags are merged at migration time using a deduplication table. If any tag taxonomy exceeds Dolibarr's native category depth, we use a multi-select extrafield on the target object instead.

EF Enterprise custom objects for exhibitor contracts, floor plans, and lead retrieval are not migratable without a direct schema export from the source Salesforce org because these objects are not discoverable via the standard REST API without metadata access. We request a Salesforce schema export during discovery. If provided, we recreate the custom object schema in Dolibarr using extrafield definitions on the nearest native Dolibarr object (e.g., exhibitor contract PDFs linked to llx_societe as document entries). Without a schema export, custom objects are flagged as unsupported and excluded from the migration scope.

EF Enterprise stores deprecated exhibitions as inactive records (a common Salesforce soft-delete pattern) rather than deleting them. We surface the full inactive Exhibition list during discovery review. Active Exhibitions map to Dolibarr project.statut = 0 (Open). Archived exhibitions map to project.statut = 1 (Closed) with an extrafield ef_archived__c = 1 to distinguish true archive state from normal closure. The customer decides for each inactive Exhibition whether it migrates as Closed or is excluded.

EF Enterprise uses undocumented Salesforce custom fields to store exhibitor contract terms, ROI tracking values, and booth pricing tier flags. Without a schema export from the source org, these fields are not discoverable via the public API. We request a Salesforce schema export during discovery and validate every custom field before building the migration map. If schema access is unavailable, we migrate only standard fields and flag the custom fields as unmigrated in the discovery report. With schema access, we recreate each custom field as a named extrafield column on llx_societe_extrafields and populate it during the Sponsor migration.