Migrate from Furious to Dolibarr ERP

Furious Client records map directly to Dolibarr Third Party (societe table). Standard fields (name, email, address, phone, website) migrate 1:1. We activate Dolibarr's Third-Party module before migration begins. The dedupe key is the client name and email combination. If Furious stores client type (prospect, customer, vendor), we map to Dolibarr's Client property (prospect, customer, supplier) on the Third Party record.

Furious Projects map to Dolibarr Project (projet table). Project status (active, completed, on-hold) maps to Dolibarr's ProjectStatus field values. Project budget and billable flag migrate to Dolibarr's Budget and Usage fields. We activate the Projects module before migration and ensure the Third Party (client) reference is resolved first so that the project-to-client linkage is satisfied at import time.

Furious Tasks belong to Projects and have assignees, status, and due dates. We map to Dolibarr Task (projet_task table) linked to the migrated Project. Task status from Furious maps to Dolibarr Task status values. Custom fields on Tasks require field-level mapping during scoping; we discover the custom field set first and create matching Dolibarr extrafields before import.

Furious Time Entries associate to a user, project, and task with billable/non-billable flags and hours. We map to Dolibarr ProjectTaskTime (projet_task_time table) linked to the migrated Project and Task. The billable flag maps to Dolibarr's invoiceable property. User mapping resolves by email match; if the user is not a Dolibarr user, we flag them for admin provisioning before the time entry import phase.

Furious Quotes contain line items tied to Projects and carry pricing, quantities, and descriptions. We map to Dolibarr Proposal (propale table) linked to the Third Party and Project. Quote status (draft, sent, accepted, lost) maps to Dolibarr Proposal status. Custom fields on Quotes require field-level mapping; we create matching Dolibarr extrafields under the Proposal module before import.

Furious Invoices reference Clients and Projects with line items and totals. We map to Dolibarr Facture (facture table) linked to the Third Party. Invoice status (draft, validated, paid, cancelled, abandoned) maps to Dolibarr's status field. Open invoices at cutover time are flagged for manual reconciliation after migration because payment status can change during the cutover window. We recommend a payment blackout period or double-bookkeeping verification post-migration.

Furious Purchase Orders link to Projects and Vendors with line items. We map to Dolibarr CommandeFournisseur (commande_fournisseur table). Vendor records must be created in Dolibarr before Purchase Order import; we identify all vendors in Furious during discovery and create Third Party records with the supplier property set before the PO migration phase begins. PO status maps to Dolibarr supplier order status.

Furious User records include name, email, and role. We map to Dolibarr User (user table). Role strings from Furious (Project Manager, Account Lead) do not map directly to Dolibarr's permission group model; we map to the closest Dolibarr permission group and flag the mapping for manual review in Dolibarr's Users → Rights interface after migration. Inactive users in Furious are excluded unless explicitly requested.

Furious custom fields on Projects, Quotes, Invoices, and Tasks require field-by-field mapping to Dolibarr extrafields. We discover the full custom field set during the discovery phase, then create matching Dolibarr extrafields under the appropriate module before any data import. Field types are mapped: text to varchar, number to integer or decimal, date to date, checkbox to yesno. Custom fields without a Dolibarr equivalent are flagged for manual entry post-migration or alternative storage as a Note.

Furious stores binary file attachments linked to Projects, Quotes, and Invoices. We do not extract or transfer these files. We audit every Furious record with an attachment during discovery and deliver a re-upload checklist that maps each attachment to its parent record and Dolibarr module for manual re-upload post-migration. This is the largest manual post-migration task for most Furious migrations.

Furious Purchase Orders reference Vendors that may not exist as standalone records. During discovery we extract every vendor referenced in Purchase Orders and create corresponding Dolibarr Third Party records with the supplier property enabled. This vendor pre-creation is a prerequisite for Purchase Order import and must complete before the PO migration phase begins.

Furious agency-specific roles (Project Manager, Account Lead) map to Dolibarr permission groups. Dolibarr permissions are module-scoped: a user can have read, create, modify, delete, and export permissions per module. We map Furious role capabilities to Dolibarr permission group assignments, but the customer must review and adjust these in Dolibarr's Users → Rights interface post-migration because the permission models are not structurally equivalent.