Migrate from Copyl to Dolibarr ERP

Copyl has no fixed schema, so every customer workspace contains unique custom objects built over time. We enumerate all custom entity definitions during scoping, then map each to either a Dolibarr standard object with ExtraFields (if the entity resembles a ThirdParty, Product, or Project) or a custom database table if no standard object fits. All custom fields on the entity are recreated in Dolibarr's ExtraFields system with matching field types. This phase determines the bulk of migration timeline because every entity must be classified before transformation begins.

Copyl Tasks map to Dolibarr Projects with task sub-elements. We preserve task titles, descriptions, status, assignees, due dates, and any custom fields. In Copyl, status values are user-defined arbitrary strings; we map each to a corresponding Dolibarr ProjectStatus value explicitly during the status mapping phase. If Copyl uses hierarchical task groups, these map to Dolibarr's Project sub-tasks. Dependencies between tasks are noted for admin review in Dolibarr rather than migrated as automation rules.

Copyl Resources represent people, equipment, or budgets allocated to tasks. We split by type: people with user accounts map to Dolibarr User records; people who are contact-only (external resources, contractors) map to Dolibarr Contact records attached to the relevant ThirdParty. Equipment and budget resources map to Dolibarr Product records or custom ExtraFields on Project depending on how the customer intends to track them. Resource allocation mappings are exported and documented for manual reconfiguration in Dolibarr.

Copyl Projects group tasks and resources and map directly to Dolibarr Projects. Project hierarchies and task associations are preserved. Project-level custom fields migrate as ExtraFields on the Project object. Budget and timeline fields map to Dolibarr's date range and budget tracking fields if the Project module is configured with those options.

Copyl workspace user accounts with roles and permissions map to Dolibarr Users. We export user identities, email addresses, role assignments, and permission levels. Role mapping requires a manual decision: Copyl's custom role definitions must be mapped to Dolibarr's permission set model (Standard User, Restricted User, Admin). User status (active/inactive) is preserved. Dolibarr requires at least one admin user for initial configuration.

Comments attached to Copyl tasks and projects migrate to Dolibarr Note records. We preserve comment text, author (linked to the mapped User or Contact), timestamp, and parent object reference. Thread ordering is maintained by sorting on the original timestamp during import. Rich text in Copyl comments is converted to HTML-safe plain text in Dolibarr Notes.

Files attached to Copyl tasks and projects are exported from the file system and re-uploaded to Dolibarr's document management system under the corresponding Project or other parent object. File metadata (name, size, type, upload date) is preserved. Dolibarr stores documents in the /documents/ directory with database references; we maintain the directory structure and linking during re-upload. If the attachment count exceeds 10,000 files, we chunk the upload to avoid server timeout.

Every Copyl workspace has custom fields defined on objects. We export the full field definition set including field type (text, number, date, picklist, checkbox), required flag, and picklist options. Each custom field is recreated in Dolibarr's ExtraFields system on the matching destination object. Field type mapping: Copyl text fields map to Dolibarr varchar or text depending on length; Copyl date fields map to Dolibarr date; Copyl picklist fields map to Dolibarr select with explicit option mapping; Copyl checkbox fields map to Dolibarr boolean. Custom field order and grouping are documented for admin review.

If the Copyl workspace contains custom objects that represent companies, clients, or organizations (common in business-management Copyl builds), these map to Dolibarr ThirdParty (also called Societe). Address, phone, email, and commercial fields migrate to the corresponding Dolibarr fields. Dolibarr's ThirdParty object supports both customer and supplier types; we determine the type from a Copyl custom field or default to Customer.

Custom objects in Copyl representing individual people (contacts, employees, decision-makers) map to Dolibarr Contact records. Contacts are linked to a parent ThirdParty if one exists. First name, last name, email, phone, job title, and address fields migrate directly. Role or department information from Copyl maps to a Dolibarr ExtraField on Contact since Dolibarr's standard Contact does not have a dedicated role field.

Custom objects representing products, inventory items, or services in Copyl map to Dolibarr Product records. We split by type: physical goods map to Product with stock management enabled; services and non-inventory items map to Service. Fields including name, description, SKU, price, and unit of measure migrate to Dolibarr's product fields. Stock levels migrate if the Product module's stock tracking is enabled in the destination.

Custom objects in Copyl representing invoices, bills, or payment records map to Dolibarr Invoice records. We migrate invoice number, date, due date, line items (mapped to FactureDet), total amount, tax amount, and payment status. Copyl's custom invoice status values (which are arbitrary strings) map explicitly to Dolibarr's predefined invoice status set (Draft, Validated, Paid, Cancelled, Abandoned). Historical invoices are imported as Closed/Paid based on the Copyl payment status.

Copyl allows users to define arbitrary status strings on any object, with no enforced picklist. Dolibarr enforces predefined picklist values per field. We enumerate every unique status value found across all Copyl objects during the schema audit, then map each to the nearest Dolibarr standard status or create a new picklist option if the destination field allows custom options. Unmapped statuses that have no Dolibarr equivalent are preserved in a custom ExtraField to maintain the original value for audit purposes.

Copyl records carry creation dates, modification timestamps, and historical dates that reflect when records were originally entered or when events occurred. We preserve all date fields as-is during migration, setting the equivalent date fields in Dolibarr records. This is important for audit trails, reporting on historical periods, and maintaining the operational continuity that the Copyl workspace provided.