Migrate from KeyedIn to Dolibarr ERP

KeyedIn Projects map directly to Dolibarr Project records. We preserve project name, status (Draft, Active, On Hold, Complete), start and end dates, and budget amounts. The KeyedIn project owner maps to the Dolibarr Project contact or user reference. Status values are translated to Dolibarr's fk_statut enumeration (0=Draft, 1=Open, 2=Closed).

KeyedIn Tasks nested under Projects map to Dolibarr ProjectTask records. Parent-child task hierarchy is preserved by ordering imports by parent task reference and resolving the fk_task_parent foreign key. Start and end dates, assignees (linked to Dolibarr User or Contact), and task status migrate directly. Subtasks at the third level are flattened into child Tasks if no third-level nesting exists in the destination Dolibarr configuration.

KeyedIn Resources (People entities used for allocation and capacity planning) map to Dolibarr User records if they are internal employees. Generic resource pool entities map to Dolibarr Third Party contacts. Resource-to-project assignments migrate as separate allocation records, which are represented in Dolibarr as Task assignments linked to the Project. Capacity and forecasting data from KeyedIn is held for customer decision since Dolibarr's project module does not include a native capacity heatmap.

KeyedIn Portfolios group related Projects for executive visibility. We migrate Portfolio-to-Project associations as Dolibarr Categories (multicateg table) or Tags depending on which module the customer has activated. The customer selects the association strategy during scoping. This preserves which projects belong to which portfolio grouping without requiring a custom junction object.

KeyedIn standalone Deliverables map to Dolibarr Project Milestone records attached to the parent Project. We resolve the parent Project reference by querying the Task Plan that the Deliverable is linked to, then tracing to the owning Project. Milestone name, due date, percentage complete, and status migrate. Milestones that have no parent Task Plan link are flagged as orphaned and held for customer resolution before import.

KeyedIn Milestones embedded within Task Plans also map to Dolibarr Project Milestone records. Where a Task Plan Milestone and a standalone Deliverable represent the same milestone (identified by matching name, date, and parent Project), we flag the duplicate pair, present it to the customer for resolution, and migrate only the resolved canonical record. This prevents double-counting in Dolibarr project progress reporting.

KeyedIn Time Entries logged against Tasks migrate to Dolibarr ProjectTaskTime records linked to the corresponding ProjectTask. Hours, date, and billable flag migrate directly. Time entries without a valid parent Task reference are held for reconciliation; the customer resolves these against the KeyedIn source before final import.

KeyedIn Enterprise financial data — budgets, cost codes, and financial line items — is migrated as a separate data plane from tasks. We map budget amounts to Dolibarr Project cost fields if the Project Cost module is activated, or to invoice and expense records in the invoicing module if the customer prefers financial tracking through invoices. Currency mismatches and missing cost codes are flagged before write. This plane requires explicit customer decision on Dolibarr module activation during scoping.

KeyedIn Risks and Issues logged at the Project level map to Dolibarr Project Note records with a type indicator (Risk vs Issue) or to the Action/Event module if the customer has activated it. Severity, status, owner, and description migrate directly. The link back to the parent Project is preserved as a foreign key reference. Risk probability and impact scores from KeyedIn are held in custom fields on the Dolibarr record if the customer requires the additional data.

Documents attached to KeyedIn Projects or Tasks are stored as file metadata with URL reference and name. We migrate the file metadata and links as Dolibarr Document records attached to the corresponding Project or ProjectTask. Actual file blobs are migrated as file transfers if the customer provides a file share or cloud storage location, or flagged for manual re-upload if extraction of binary files is not available from the KeyedIn deployment.

KeyedIn tenant-specific custom fields are discovered during the discovery phase and mapped to Dolibarr ExtraFields on the corresponding object (Project, ProjectTask, ThirdParty). We create the ExtraField definition in Dolibarr with the correct type (string, integer, select, date, etc.) before importing data, ensuring no custom field data is silently dropped. Fields with no Dolibarr equivalent are held in a catch-all custom field group for customer decision.

KeyedIn status values representing pipeline or workflow stages (Draft, Active, On Hold, Complete) are enumerated values that map to Dolibarr's fk_statut values on Project. We generate a status mapping table during scoping, present it for customer confirmation, and apply the mapping during migration. Any KeyedIn custom status values without a Dolibarr equivalent are either mapped to the nearest standard status or flagged for custom status extension in Dolibarr.