Migrate from Stride ERP to Dolibarr ERP

Stride's standard parent-child COA maps to Dolibarr's accounting chart with account codes and names transferred directly. The destination's segment structure may differ by the configured accounting plan (Plan Comptable for French contexts, custom for others), so we flat-map the hierarchy during initial load and flag any Stride accounts that use segments (cost center, department) not present in the destination's chart. Account types (asset, liability, equity, revenue, expense) are mapped to Dolibarr's account categories during import.

Stride Customer records map to Dolibarr Third Parties with the Customer category flag enabled. Contact details, billing and shipping addresses, and payment terms transfer as-is. Credit limit from Stride maps to Dolibarr's customer credit limit field. We flag any soft-deleted Stride customers to prevent importing inactive records. The dedupe key is the customer code or email address.

Stride Vendor records map to Dolibarr Third Parties with the Supplier category flag. AP aging balances transfer as vendor-level reference data. Soft-deleted vendors are excluded from the export. The dedupe key is vendor code or tax ID.

Outstanding customer invoices from Stride (Accounts Receivable) map to Dolibarr Customer Invoice records. Invoice numbers, line items, payment terms, discount codes, and due dates preserve during import. The fiscal period in Stride is mapped to the Dolibarr date and accounting period. We sequence the import to load invoices after the customer Third Parties are in place so the customer_id foreign key resolves on insert.

Outstanding vendor invoices from Stride (Accounts Payable) map to Dolibarr Supplier Invoice records. The same sequencing logic applies: vendors must be loaded first. Credit memos and debit notes map to Dolibarr's credit note and reversal invoice types.

Stride Fixed Asset records include location assignments, depreciation schedules, and accumulated depreciation balances. We extract the depreciation history table separately and reconstruct book value using Dolibarr's native depreciation engine, which supports multiple depreciation methods (linear, declining, units-of-production). Country-configured depreciation methods from Stride (Nigeria vs Canada tax rules) are mapped to the closest Dolibarr-equivalent method during import.

Stride SKU-level items map to Dolibarr Products (both Stockable and Service types). We handle the multi-location inventory gotcha by requesting the detailed inventory ledger with warehouse location codes from Stride support separately from the standard export, then enabling Dolibarr's multi-warehouse stock module and loading per-location quantities into the correct Dolibarr warehouse records. Reorder points and current stock levels transfer to the product stock card.

Stride Employee records map to Dolibarr HRM module users with the Employee flag. Department assignments, job titles, employment status (active, terminated), and contact details preserve. Active and terminated employees are loaded separately to preserve employment history. Dolibarr's HRM module must be installed and enabled before this object imports; we confirm the module state during scoping.

Stride payroll runs and compensation history do not map to live Dolibarr payroll entries because Dolibarr's HRM payroll module handles active payroll processing differently from Stride's historical record format. We load payroll history as a reference document (attached to the employee record) rather than as a live payroll entry, mapping pay periods and Stride deduction codes to a structured notes format. The customer reconfigures payroll in Dolibarr's HRM for ongoing processing.

Stride Project records map to Dolibarr's Projects module (commercial add-on on dolistore.com or included in some partner packages). Status, assignees, milestones, task hierarchies, billable rates, and project budgets transfer. Custom fields on projects map to Dolibarr extrafields. If the destination Dolibarr instance does not have the Projects module enabled, we flag this during scoping and it becomes a module procurement decision before migration.

Stride Support Ticket records map to Dolibarr's Tickets module (commercial add-on). Ticket status, assignee, customer association, and conversation history transfer. SLA configuration from Stride does not migrate and must be re-established in Dolibarr's ticket settings. If the destination does not have the Tickets module, tickets are documented as a separate migration scope requiring module procurement.

Stride Document Management System attachments are file-level exports that we associate with their parent object (Project, Third Party, Employee) in Dolibarr via the document management feature. File naming conventions in Stride vary by use case, so we preserve the original file names and map them to the appropriate Dolibarr entity directory structure.

Purchase Requests in Stride are an add-on module and may not exist on Basic tier accounts. Where they exist, we map approval workflows and line items to Dolibarr's Supplier Proposal or Purchase Order schema, preserving approval status and requestor information. The destination module (Proposals or Purchases) is determined during scoping based on the customer's workflow.