Migrate from Clear Enterprise to Dolibarr ERP

Clear Enterprise Contact records map directly to Dolibarr Contact (llx_socpeople) linked to a parent Third Party (llx_societe). Name, email, phone, address, and owner assignment migrate as standard fields. The contact_is_customer flag in Clear Enterprise determines whether the parent Third Party is typed as customer, supplier, or both. Role or department fields from Clear Enterprise map to the Dolibarr contact Poste (position) field. Owner resolution uses email matching against the Dolibarr User table.

Clear Enterprise Company records map to Dolibarr Third Parties. Company name maps to the nom field, address and city map to address fields, and phone maps to phone. The company's domain name maps to the url field for reference. The company_id reference on Contact records is resolved at migration time so that the llx_socpeople.fk_soc foreign key points to the correct parent Third Party row. If Clear Enterprise represents customers and suppliers as separate objects, they map to client=1 and/or fournisseur=1 flags on the same Third Party record in Dolibarr.

Clear Enterprise Projects map to Dolibarr Project (llx_projet). Project name, description, status, start date, and end date migrate directly. Parent-child project hierarchies (sub-projects) in Clear Enterprise map to the parent_id reference in Dolibarr's Project table if the Clear Enterprise deployment uses project nesting. Billable flag from Clear Enterprise maps to the billed flag in Dolibarr Project. The project public or private visibility setting maps to the public flag in Dolibarr.

Clear Enterprise Tasks map to Dolibarr Tasks (llx_projet_task). Parent-child task hierarchies (sub-tasks) migrate via the fk_task_parent reference. Task fields (name, description, start date, end date, status, priority) map to Dolibarr equivalents. Custom task fields from the Clear Enterprise deployment are stored using the Dolibarr CustomFields module (llx_customfields), preserving the property name and data type. The fk_projet foreign key links each Task to its parent Project in Dolibarr.

Documents attached to Projects, Tasks, Contacts, Companies, and Custom Objects in Clear Enterprise are exported as individual files and re-associated to the correct parent record in Dolibarr. Dolibarr stores documents in the documents directory with a naming convention based on the object type and record ID. We replicate the file directory structure and update Dolibarr's extrafiles and content maps so that clicking the attachment icon in the Dolibarr UI displays the correct file. Document metadata (filename, upload date, uploader) is recorded in Dolibarr's llx_document_model or stored as extra fields.

Clear Enterprise Custom Objects have no direct Dolibarr equivalent because Dolibarr's core does not include a generic custom object type. We handle this by discovering every Custom Object type during schema profiling, then creating Dolibarr CustomFields entries (using the stable CustomFields module) on the nearest standard object — typically Project, Task, Third Party, or Contact — that matches the logical domain. For example, a Clear Enterprise custom object tracking Equipment assignments might map to Project with extra fields for equipment_id and assignment_date. We document every Custom Object mapping in the schema design phase and deploy the CustomFields schema to a Dolibarr sandbox before production load.

Clear Enterprise Users map to Dolibarr Users (llx_user) by email address match. First name, last name, email, and active status migrate directly. Role and permission translation requires per-implementation review because Clear Enterprise role definitions are custom and Dolibarr uses a simpler permission model (global permissions for admin, read, write, and delete on per-module basis). We map Clear Enterprise role names to the nearest Dolibarr permission set and flag any role that cannot be translated for the customer's admin to resolve post-migration.

Clear Enterprise Teams aggregate Users and may control access scoping. Dolibarr has a User Group concept (llx_usergroup) for grouping users. Where Clear Enterprise teams represent hierarchical access control (nested teams), we flatten the hierarchy into Dolibarr User Groups and assign the group's members accordingly. Team-specific permissions are mapped to Dolibarr module-level permissions where applicable. If the Clear Enterprise deployment uses teams to restrict record visibility (shared ownership model), we document this for the customer's admin to implement using Dolibarr's user permission rules post-migration.

If the Clear Enterprise deployment includes GL data, Chart of Accounts, or financial transactions, we map them to Dolibarr's accounting module. Dolibarr's accounting functionality requires the Accounting Expert module to be activated. Account codes from Clear Enterprise map to account_number in llx_accounting_account, and transaction amounts map to llx_accounting_bookkeeping. Currency, tax codes, and effective-dated balances require careful field-to-field translation during the ETL pipeline build. If the Clear Enterprise deployment does not include a formal chart of accounts (many SMB-focused deployments do not), this object is skipped and noted in the scope document.

Clear Enterprise standard objects (Contacts, Companies, Projects, Tasks) may carry custom fields beyond the platform defaults. We discover all custom fields during schema profiling and use Dolibarr's CustomFields module to recreate them as extra fields on the equivalent Dolibarr standard object. Field types are mapped: text fields to varchar, numbers to integer or float, dates to datetime, checkboxes to yesno, dropdowns to select. The CustomFields module stores these in separate tables (llx_customfields) that hook into the standard Dolibarr object lifecycle, so create, read, and update operations work natively in the Dolibarr UI.

Clear Enterprise engagement records (if present in the deployment) map to Dolibarr's Task, Event, and Note objects. Calls map to Task with type=phone; emails map to Event records or Note depending on the engagement type in Clear Enterprise; meetings map to Event records with start and end timestamps and location. Each engagement's parent reference (project, task, contact, or company) is resolved at migration time so that the activity appears in the correct context within Dolibarr. Historical timestamps are preserved in Dolibarr's date field on the relevant object.

Clear Enterprise relationships between records (Contact-to-Company, Task-to-Project, Document-to-Parent) are preserved through foreign key lookups during migration. We build a reference resolution table as part of the ETL pipeline: each Clear Enterprise record ID is mapped to its corresponding Dolibarr record ID after insertion, and subsequent imports use the resolved destination ID rather than the source ID. This ensures that the relationship graph in Dolibarr matches the original Clear Enterprise structure — a Contact correctly attached to its Company, a Task correctly linked to its Project, a Document correctly attached to its parent record.