Migrate from Scopevisio to Dolibarr ERP

Scopevisio Customer master records map to Dolibarr Third Party with the Customer checkbox enabled. Address, communication, and classification fields transfer 1:1. We handle Scopevisio's multi-address structures by designating the primary address and flagging secondary addresses in Dolibarr's dedicated address table. Tax identification numbers (Steuernummer/USt-IdNr) map to the Third Party fiscal identification fields. Classification codes from Scopevisio become Dolibarr categories that we create and assign during import.

Scopevisio Vendor records mirror Customer master data structure and map to Dolibarr Third Party with the Supplier checkbox enabled. Banking details (IBAN, BIC) migrate to Dolibarr's bank account fields on the Third Party. Payment terms from Scopevisio (e.g., 30 days, 60 days net) map to Dolibarr's payment term setup. We deduplicate against any existing Customer Third Parties by matching on tax ID or email domain.

Scopevisio's hierarchical chart of accounts with German SKR types (SKR03, SKR04), tax codes, and cost-centre flags requires transformation. Dolibarr has no native SKR preset, so we map Scopevisio's account type (asset, liability, equity, revenue, expense) to Dolibarr's account categories and flag any German tax-relevant accounts with a custom label. Each company in a Scopevisio multi-company setup has its own chart; we extract each as a separate import set and note which accounts are inter-company vs per-entity.

Outgoing invoices from Scopevisio map to Dolibarr Customer Invoice; incoming invoices map to Dolibarr Supplier Invoice. Scopevisio stores invoice status and document status separately; we preserve both as Dolibarr's status and payment status fields. Line items carry product reference, quantity, unit price, VAT rate, and discount; these map to Dolibarr invoice lines with the product/service linked. Open invoices retain open status; paid invoices carry payment date and payment method from Scopevisio's payment ledger entries.

Scopevisio Projects export with their hierarchy, billing method, and associated cost centres. We map project-stage statuses to Dolibarr Project status values and carry forward custom project fields as Dolibarr extra fields. If Scopevisio projects use hierarchical sub-project structures, Dolibarr's task/sub-task model within a Project accommodates the relationship. Projects without Scopevisio DMS documents are imported first; projects with document associations are queued until the document import phase completes.

Scopevisio time entries associate project, employee, date, hours, and optionally billing rate. We map each entry to a Dolibarr Task under the corresponding Project with the time recorded in hours and the employee linked via User ID. Billable/non-billable flags from Scopevisio map to Dolibarr's billable task flag. If Scopevisio time entries reference a service or product for billing, we create the corresponding Product in Dolibarr and link the task for invoicing.

Scopevisio's DMS/ECM layer stores documents linked to business objects. We export files in original format (PDF, Office, images) and re-associate them in Dolibarr ECM with the correct object reference (Third Party, Project, Invoice, or Task). File naming conventions and Scopevisio folder structures become Dolibarr directory labels. Large files (over 10 MB) are chunked; files with non-standard characters in filenames are sanitized. We preserve Scopevisio's document metadata (created date, author) as file properties.

Scopevisio HR module employees map to Dolibarr User records for system access and to the HR Employee module (if enabled) for personnel data. Organisational hierarchy from Scopevisio maps to Dolibarr User reporting lines (subordinate/manager relationships). PTO balances and effective-dated compensation records migrate as HR extra fields; we note that Dolibarr's HR module handles basic leave tracking and salary but is less feature-rich than Scopevisio's dedicated HCM module.

Scopevisio Items export with pricing, unit of measure, stock-control flags, and optionally BOM structures. We map item codes to Dolibarr Product ref, descriptions to label, and pricing tiers to Dolibarr price lists. Stock-control flags activate Dolibarr's warehouse module; BOM structures note as a custom flag since Dolibarr's manufacturing module handles bill of materials separately. Any custom pricing tiers are written as separate price list rows in Dolibarr.

Scopevisio fixed asset records carry acquisition cost, depreciation method, depreciation schedule, and location. These map to Dolibarr Asset records with the acquisition date, value, and depreciation method preserved. We flag any assets with partial depreciation as open assets and note their remaining book value. Some destinations handle asset depreciation differently; we document the Scopevisio depreciation schedule as a custom field for the customer's accountant to verify against German commercial code (HGB) requirements.

Scopevisio custom fields on standard objects (Customer, Invoice, Project, Employee) map to Dolibarr Extra Fields with type translation: date fields become date, text fields become varchar, picklist fields become select. We discover all custom field definitions during scoping, map them to Dolibarr extrafield definitions, and note any type differences that require data transformation (e.g., multi-select picklists in Scopevisio become multi-checkbox extra fields in Dolibarr).

File attachments on any Scopevisio object export as binary blobs paired with their parent record reference. We map each file to a Dolibarr document attached to the equivalent object (Third Party, Project, Invoice, or Task). Dolibarr's file-size limit per upload defaults to 8 MB; larger attachments are flagged for split or hosted-link replacement. Dolibarr's native document indexing and full-text search covers imported files after re-attachment.