Migrate from Selly Erp to Dolibarr ERP

Selly Erp Customer records map to Dolibarr ThirdParty (societe) objects with a direct field-to-field mapping for company name, address, postal code, city, country, phone, email, and VAT number. The customer type distinction (customer versus prospect versus supplier) maps to Dolibarr's Client, Prospect, or Fournisseur classification. Company domain from Selly's website field populates the ThirdParty url. Multi-address customer records require one ThirdParty per address in Dolibarr, and we extract all address records during scoping to split them correctly.

Selly Erp Contact records (first name, last name, email, phone, job title) map directly to Dolibarr Contact records. Each Contact is linked to a parent ThirdParty via the srowid (fk_soc) foreign key, which we resolve by matching the ThirdParty name or company email domain during the import phase. The Contact's primary flag from Selly sets the isprimary() status in Dolibarr. Custom fields on Contact map to Dolibarr extrafields in the llx_socpeople_extrafields table.

Selly Erp Leads with unqualified status map to Dolibarr ThirdParty records with the Prospect client type (prospect = 2) rather than the Customer type. We set the prospect status during import so that Dolibarr's CRM pipeline can treat these records as pipeline entries. Lead source and score data from Selly map to custom fields that we pre-create in Dolibarr's extrafields schema before the import runs.

Selly Erp Deals map to Dolibarr Commercial Proposals (Propal). The deal name, estimated value, currency, expected close date, and owner all transfer directly. Selly's deal stage (won, lost, open) maps to Dolibarr Proposal status (Draft, Open, Signed, Closed Won, Closed Lost). Closed-Lost and Closed-Won reasons from Selly custom fields become notes on the Dolibarr Proposal record. We flag any multi-currency deal values for currency conversion before import into Dolibarr's euro-default configuration.

Selly Erp pipeline stage names are stored as a configurable list per account and map to Dolibarr's dictionary table (llx_c_departements_planning or llx_c_stde) or the Proposal status dictionary. We extract the complete stage list during scoping, create matching entries in Dolibarr's dictionary administration panel, and assign numeric codes that the Proposal import references by rowid. Stage ordering and probability percentages carry over as dictionary labels and the probabilite field on Proposals.

Selly Erp invoice records map to Dolibarr Invoice (Facture) objects. We extract invoice number, date, due date, customer reference (ThirdParty), line items (description, quantity, unit price, VAT rate), totals, and payment status. Currency and date formats require pre-import transformation because Dolibarr's date field regex enforces strict YYYY-MM-DD HH:MM:SS formatting. The original invoice PDF is archived separately and linked to the Dolibarr Invoice record as a document attachment for reference; the structured line-item records carry the accounting value.

Selly Erp Quotes map to Dolibarr Commercial Proposals with identical field coverage: line items, totals, validity date, and reference to the parent ThirdParty. Quote status from Selly (draft, sent, accepted, expired) maps directly to Dolibarr Proposal status codes. Custom quote templates and branded layouts from Selly do not transfer and must be rebuilt in Dolibarr's document template editor after migration. We deliver a written template specification noting fonts, colors, and layout from the source export.

Selly Erp Activity history (calls, emails, meetings, tasks, notes) maps to Dolibarr Event records linked to the parent Contact or ThirdParty via the fk_soc and fk_contact foreign keys. We set the event type (call, meeting, email, task) using the fk_element_type code and preserve the original timestamp in the datep and datep2 fields. Note body content transfers as an Event with type NOTE, linked to the appropriate record. Activity metadata such as call duration or email subject line migrates to Event's description field or to custom extrafields we pre-create before import.

Selly Erp user accounts map to Dolibarr User records by email address match. We extract all distinct owner identifiers on Deals, Invoices, and Activities and reconcile them against Dolibarr's llx_user table before the main import begins. Inactive or archived Selly users receive the Dolibarr status that matches their source account status. Owner assignment on Deals and Invoices resolves to the matching Dolibarr User rowid at migration time. Any Selly owner without a Dolibarr user match enters a reconciliation queue for the customer's admin to provision.

Selly Erp custom fields on any object map to Dolibarr extrafields in the llx_<table>_extrafields tables. We extract the full list of custom field names, data types, and values during scoping, then pre-create the matching Dolibarr extrafield definitions (type, label, param options for dropdowns) via the Dolibarr setup interface or direct database insert before any data loads. Dropdown values from Selly's custom field options map to Dolibarr's param options structure so that enumerated values render correctly in Dolibarr forms.

File attachments linked to Selly Erp records (Customer, Contact, Deal, Invoice) are extracted from the export dump and stored in a secure archive. We do not load them through Dolibarr's bulk import because attachments frequently fail or corrupt during batch processes. After the main migration completes and records have Dolibarr rowids, we provide a file-to-record mapping spreadsheet and instructions for the customer's admin to re-upload documents using Dolibarr's native file attachment interface. The original file names and record associations are preserved in the archive.

Selly Erp Quotes are generated from Deal records and carry the deal reference. During import, we preserve the deal-to-quote relationship by matching the Quote's external reference field to the Deal's external reference, then store the cross-reference in Dolibarr's ref_ext field on both the Proposal and any linked Deal-equivalent records. If the customer is not using Dolibarr's full project or Opportunity tracking, the Proposal record serves as the standalone commercial record and the relationship is informational rather than enforced by a foreign key.