Migrate from Exxas Cloud Business Platform to Dolibarr ERP

Exxas person-level contacts in the Central module map to Dolibarr Contact records. We extract all standard fields (name, email, phone, address) plus any custom data mask fields attached to the contact entity. German-language field labels are translated to English equivalents during preprocessing. The Dolibarr Contact is linked to a Dolibarr Thirdparty (Company) record via the sconid field. Note that Dolibarr Contact does not have a direct equivalent to Exxas's 360-degree contact view; contact information is distributed across Contact, Address, and Thirdparty records.

Exxas company records in the Central module map to Dolibarr Thirdparty records. Exxas company-level custom fields (industry tags, D-U-N-S number, corporate group membership) map to Dolibarr extrafields. The Exxas company domain used for contact deduplication becomes the Thirdparty website field. We create the Thirdparty before Contact migration so the sconid lookup is satisfied at insert time.

Exxas deal records with associated pipeline stages map to Dolibarr Commercial Proposals (for pre-close deal data) or Dolibarr Projects (for post-sale ongoing deal tracking). The mapping decision is made during scoping based on whether the customer treats Deals as sales-in-progress records or project-linked work orders. Exxas deal custom fields (margin calculation fields, competitor tracking) migrate as Dolibarr extrafields. We configure Dolibarr CRM tags to replicate Exxas pipeline stage labels when CRM mode is activated.

Exxas interested parties (Leads in Exxas Sales terminology) with status prior to sales qualification map to Dolibarr Thirdparty records with the Prospect customer type flag set. We preserve Exxas lead score and lead source fields as Dolibarr extrafields. The Exxas task-package and workflow attachments associated with lead nurturing do not migrate; we document them for manual rebuild in Dolibarr's Workflow module.

Exxas Service module tickets map to Dolibarr Ticket records when the Dolibarr Service module (service management) is activated. Ticket status, priority, assignment, and linked customer assets migrate. Exxas subscription and maintenance contract records map to Dolibarr contract records. If the Dolibarr Service module is not activated, tickets map to Project-linked Task records as an alternative. Conversation threads migrate as Note records attached to the ticket or task.

Exxas project records with their associated task hierarchies, Kanban board data, and time entries map to Dolibarr Project and Task records. Sprint assignments are stored as a Dolibarr project extrafield since Dolibarr lacks a native sprint concept. Resource planning assignments migrate as Task resource entries. Exxas Gantt chart data (project plan start/end dates, dependencies) maps to Dolibarr project date fields and task date ranges. Burndown metrics are not transferred as they are calculated metrics rather than stored records.

Exxas product records with pricing tiers, SKU codes, and stock-on-hand values map to Dolibarr Product records and Stock entries. BOM (bill of materials) relationships migrate to Dolibarr's manufacturing module if activated. Exxas warehouse-specific bin locations and multi-warehouse stock assignments require manual reconciliation in Dolibarr's Stock module post-migration because bin-level granularity may not map cleanly across different warehouse setups.

Exxas employee profiles, job titles, department assignments, and effective-dated compensation history map to Dolibarr User records and HR module entries. Employee expenses and absence management migrate to Dolibarr expense reports and leave requests. Exxas working-time measurement entries map to Dolibarr timesheets. We flag any country-specific benefit fields (BVG pension, health insurance assumptions) for manual review because Dolibarr's HR module uses a more generic model. Exxas payroll run data does not migrate as described in the gotchas section.

Exxas Finance module account structure, open AP and AR items, and current-period journal entries map to Dolibarr's double-entry accounting module. The account code structure requires a schema review because Dolibarr ships with French/EU chart-of-accounts templates and Exxas uses Swiss account numbering conventions. We provide a mapping spreadsheet during scoping and configure the Dolibarr chart of accounts to match the customer's existing structure before migration. Historical closed-period journal entries migrate as read-only entries; open AP/AR items migrate as active records with partner (supplier/customer) references resolved to Dolibarr Thirdparty records. Multi-currency support is enabled in Dolibarr accounting if the customer uses CHF, EUR, or USD in Exxas.

Exxas marketing campaign records and lead flow assignments map to Dolibarr Mailing (email campaign) records and CRM tag assignments. Exxas campaign member status (sent, opened, converted) migrates as Dolibarr MailingCampaign recipient records. Note that Dolibarr's native marketing module is more limited than Exxas's integrated Marketing module; complex campaign logic, A/B testing configurations, and lead scoring models require manual rebuild in Dolibarr's workflow or an external marketing automation tool. We document the original campaign structure in the handoff inventory.

Exxas custom data mask definitions (individual fields per entity category) migrate to Dolibarr extrafields with appropriate type mapping: string fields to Dolibarr varchar, numeric fields to int or float, date fields to datetime, and checkbox fields to boolean. We pre-create all extrafield definitions in Dolibarr before any data import so that destination fields are available at insert time. If Dolibarr's standard extrafields system cannot represent a particularly complex Exxas custom field type, we flag it during scoping and propose an alternative approach (separate lookup table, text serialization, or manual post-migration entry).

Exxas personal customer portal records (invoices, orders, support tickets, and asset documentation facing the end customer) migrate as Dolibarr Thirdparty-linked records in document management. Portal configuration settings (branding, access rules, portal-specific layouts) do not migrate because Dolibarr uses a different portal framework. We migrate the underlying data and flag the configuration gap in the handoff document.