Migrate from Maximum Software to Dolibarr ERP

Maximum Software Customer records map to Dolibarr ThirdParty entities with the Third Party type set to Customer. The source customer name maps to the required name field, and address, phone, and email map to the corresponding contact fields. Dolibarr's dedupe check uses email as the unique key; we resolve any Maximum Software customers sharing an email address by appending a disambiguating suffix before import. The source's customer-specific fields (payment terms, credit limit) map to Dolibarr's Payment Terms and Maximum Recommended Payment Delay settings on the ThirdParty record.

Maximum Software Vendor records map to Dolibarr ThirdParty entities with the type set to Supplier. The vendor name, address, and contact information migrate directly. We flag any Maximum Software vendor that shares an email with an existing customer record and surface the conflict for the customer's admin to resolve before import, because Dolibarr does not allow a single ThirdParty to be both Customer and Supplier simultaneously without module configuration changes.

Maximum Software chart-of-accounts records map to Dolibarr's accounting module configuration. Each account code maps to a Bank Account or Account record in Dolibarr depending on the account type (asset, liability, equity, income, expense). We flag accounts with non-numeric characters or lengths exceeding Dolibarr's account code format (typically 6-8 digits) for manual review and code normalization. Dolibarr's accounting module must be enabled and configured before invoices are imported, because invoice lines reference account codes that must exist at import time.

Maximum Software Items map to Dolibarr Product records. The source item type (goods vs. service) maps to Dolibarr's ProductType field. The source SKU maps to ref, and description maps to label. If the Maximum Software item carries stock quantities, we require the Dolibarr Stock module to be activated before migration because Dolibarr stores stock as a separate module-level concern and items without the Stock module enabled cannot carry real-time inventory quantities. Cost price from Maximum Software maps to the PMp field (cost price) in Dolibarr.

Items with active inventory tracking in Maximum Software map to Dolibarr Product records with the Stock module enabled and warehouse-level quantity records created during import. We create a default warehouse (Warehouse ID 0) if one does not exist in the Dolibarr destination. The source's current stock quantity, reorder point, and unit of measure map to the corresponding Dolibarr stock record fields. Any items with negative stock in Maximum Software are flagged as exceptions before import because Dolibarr's stock module does not natively support negative inventory without explicit configuration.

Maximum Software open invoices (accounts receivable) map to Dolibarr Customer Invoice records with status set to Draft or Unvalidated. The invoice number, date, due date, line items, and total amounts migrate. Payments already applied to invoices in Maximum Software are not recreated as separate payment records in Dolibarr; instead, the paid amount is noted in an invoice-level custom field and the invoice status is set to Paid if fully settled, or Partial if partially paid. Invoice PDFs from Maximum Software are stored as ContentDocument linked to the corresponding Dolibarr invoice.

Maximum Software vendor bills (accounts payable) map to Dolibarr Supplier Invoice records. The vendor is resolved via the ThirdParty lookup (Vendor-to-Supplier mapping). Line items map by matching the Maximum Software item reference to the imported Product record. Paid status is set consistent with the Maximum Software payment state. Historical paid invoices with no open balance are imported with status Validated and Closed for audit trail completeness.

Maximum Software User records map to Dolibarr User accounts. The source user's email becomes the login, and the active/inactive status maps to the Dolibarr account status. We resolve the Maximum Software user role (admin vs. standard) to Dolibarr permissions flags (Read/Write/Delete/Print/Export per module). Any Maximum Software user without a valid email is assigned a generated placeholder email for migration compatibility and flagged for the admin to update post-migration.

Maximum Software call records map to Dolibarr Intervention records (if the Interventions module is enabled) or Agenda Event records (if only Agenda is enabled). The call direction, duration, date, and disposition migrate to the corresponding fields in the destination. The linked contact or vendor is resolved via the ThirdParty lookup by email or name match. Calls without a resolvable ThirdParty link are imported as standalone interventions and flagged for the admin to reconnect manually.

Maximum Software meeting records map to Dolibarr Agenda Event records. The meeting title, scheduled date and time, duration, location, and attendee list migrate to the corresponding Event fields. Attendees are resolved as EventRelation records pointing to the matching ThirdParty (Customer or Supplier) or User in Dolibarr. Any attendee not resolvable in Dolibarr is stored as plain text in the Event's note field and flagged for review.

Maximum Software task records map to Dolibarr Agenda Task records with the task subject, due date, priority, status, and assigned user migrated. The assigned user is resolved via email match against the Dolibarr User table. Completed date and completion status migrate as the task's done date. Tasks without an assignable user in Dolibarr are imported as unassigned tasks and flagged in the reconciliation report.

Maximum Software project or job records map to Dolibarr Project records. The project name, description, start date, end date, status, and budget migrate directly. If the Maximum Software project has associated tasks or time entries, these map to Dolibarr ProjectTask and ProjectTaskTime records respectively. The Projects module must be enabled in Dolibarr before this object import runs; we verify module activation during the discovery phase and surface any missing module dependencies as a pre-migration action item.

Maximum Software custom field values map to Dolibarr ExtraFields attached to the corresponding record. Dolibarr's CustomFields module requires the field to be pre-created in the destination before data can be stored; we create the ExtraField definition (with type matching: string, int, float, select, checkbox, date) before importing records that carry the custom field. Constrained custom fields (fields pointing to other records) use Dolibarr's fk_moduleid lookup semantics, which requires the referenced record's rowid to be available at migration time. We resolve this by pre-importing parent records and using the assigned Dolibarr rowid as the foreign key value.

Maximum Software workflows and automations do not migrate as executable code to Dolibarr because the automation models differ. We deliver a written inventory of every active Maximum Software workflow, trigger condition, action, and automation rule. The inventory includes a recommended Dolibarr equivalent using Dolibarr's Triggers (automatic actions per module) or external tools. The customer's admin rebuilds automations in Dolibarr post-migration as part of the onboarding configuration scope. Workflows and automations are outside the data migration scope by design.