ERP migration
Field-level mapping, validation, and rollback between CLEAR Media ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
CLEAR Media ERP
Source
Dolibarr ERP
Destination
Compatibility
8 of 12
objects map 1:1 between CLEAR Media ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from CLEAR Media ERP to Dolibarr is a structural migration from a media-production platform to a general-purpose open-source ERP. CLEAR organises data around Productions, Work Orders, Dailies, and Assets on the DAX backend; Dolibarr uses Projects, Tasks, Third Parties, Products, and Invoices. There is no documented public API for CLEAR, so we build a session-based scraper to extract structured records from the DAX web UI, which requires stability assumptions about the source interface. We map Dailies to Projects with custom fields for shoot-date metadata, Assets to Dolibarr document records with custom fields for format and resolution, Work Orders to Tasks with project linking, and Productions to Projects with date ranges. CLEAR's Work Order billing sub-system carries financial values that must be entered as Dolibarr Invoices or billable time entries post-migration because Dolibarr lacks an embedded Work Order billing construct. We do not migrate DAX workflows, production automations, or review-platform configurations; these require manual rebuild in Dolibarr.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a CLEAR Media ERP object lands in Dolibarr ERP, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
CLEAR Media ERP
Productions
Dolibarr ERP
Projects
1:1CLEAR Productions map to Dolibarr Projects. Each Production carries a name, type (feature, series, commercial), and date range that transfer to Project name, description, and date fields. We map the Production type to a Project category or tag in Dolibarr to preserve classification. Productions serve as top-level containers in CLEAR, equivalent to Projects in Dolibarr, so the 1:1 mapping is straightforward provided the destination instance has the Project module activated.
CLEAR Media ERP
Dailies
Dolibarr ERP
Projects (custom fields)
1:1CLEAR Dailies records do not have a direct Dolibarr equivalent. We map Dailies to a secondary Project record or a Project sub-task, with shoot date, unit, and sequence metadata stored in custom fields on the Project. The Dailies-to-Asset version relationship is preserved as a note attachment. We flag that Dailies are daily footage groupings that have no native Dolibarr construct; the mapping relies on custom field activation in Dolibarr and agreement on metadata taxonomy during scoping.
CLEAR Media ERP
Assets
Dolibarr ERP
Products (with document link)
1:1CLEAR Assets (cuts, playlists, masters, proxy files) map to Dolibarr Products with document attachments. Format, resolution, codec, and transcoding status transfer to custom fields on the Product record since Dolibarr's standard Product object does not include media-specific fields. Asset URLs pointing to cloud storage are preserved as external URL fields; if cloud access is revoked post-migration these links become orphaned, and we flag this during scoping.
CLEAR Media ERP
Work Orders
Dolibarr ERP
Tasks
1:manyCLEAR Work Orders map to Dolibarr Tasks linked to the corresponding Project. Assignees, due dates, status, and asset references transfer. A single CLEAR Work Order may reference multiple Assets, which we split into separate Task-Product links in Dolibarr. Work Order type (creative task vs machine-rendered task) maps to a Task category or tag. Note: Dolibarr Tasks do not natively support the billing sub-system that CLEAR embeds in Work Orders; billed amounts are held for post-migration invoice entry.
CLEAR Media ERP
Users
Dolibarr ERP
Users
1:1CLEAR Users transfer to Dolibarr Users by email match. Display name, email, and internal role transfer cleanly, but permissions and access scopes are destination-specific. We map CLEAR role names to the closest Dolibarr permission group (Admin, Standard, Read-only) and flag any roles without a clear Dolibarr equivalent for the customer's admin to configure post-migration. External collaborators without an email login in CLEAR map to Dolibarr Contacts if they need to receive task notifications.
CLEAR Media ERP
Customers / Vendors
Dolibarr ERP
Third Parties
1:manyCLEAR Customers and Vendors both map to Dolibarr Third Parties, using the Supplier contact type for vendors and Customer type for clients. Address, email, phone, and entity type transfer. Any CLEAR-specific billing fields not present in the source record are flagged and omitted. We recommend separating Customers and Vendors into distinct Third Party categories during migration to preserve entity taxonomy; this is a configuration step in Dolibarr.
CLEAR Media ERP
Items
Dolibarr ERP
Products
1:1CLEAR Items (deliverables, equipment, services tracked for billing within a Production) map to Dolibarr Products. Unit cost, description, and item type transfer directly. Custom Items properties migrate to Dolibarr extra fields on the Product record. If the Production carries Items with billing amounts, we note these for Work Order billing reconciliation in the post-migration invoice phase.
CLEAR Media ERP
Documents
Dolibarr ERP
Documents (linked to Projects/Tasks)
1:1CLEAR Documents (contracts, briefs, approval sign-off sheets attached to Productions or Work Orders) migrate as Dolibarr document records linked via the document management module to the corresponding Project or Task. We extract name, type, date, owner, and the file reference. If the original files are stored in CLEAR's cloud storage, we preserve the URL; if the files themselves are needed, that requires a separate file-transfer scope.
CLEAR Media ERP
Approvals / Sign-offs
Dolibarr ERP
Custom fields or Notes on Projects/Tasks
lossyCLEAR approval chains (approver, timestamp, decision) do not have a native Dolibarr equivalent. We map approval status to a custom field or structured note on the Project or Task record, capturing the approver name, decision (approved/rejected), and timestamp. If the customer requires formal approval workflows in Dolibarr, the Approval module must be activated and configured post-migration; this is outside the data-migration scope.
CLEAR Media ERP
Chart of Accounts
Dolibarr ERP
Not applicable
1:1CLEAR does not expose a general-purpose Chart of Accounts. Financial ledgers are managed within the Work Order billing sub-system and are not independently exportable. We do not migrate Chart of Accounts from CLEAR. If the customer needs a financial chart in Dolibarr, we recommend setting it up from a standard template post-migration rather than migrating from a closed source.
CLEAR Media ERP
Bank / Cash Accounts
Dolibarr ERP
Not applicable
1:1CLEAR does not expose treasury or bank account objects. Open AP/AR balances are not stored as independent records and cannot be migrated as such. We flag this gap and recommend establishing Dolibarr bank accounts from scratch post-migration.
CLEAR Media ERP
Work Order billing amounts
Dolibarr ERP
Invoices (manual post-migration)
lossyWork Orders carrying financial billing values require post-migration invoice entry in Dolibarr. We extract the billed amount, currency, and Work Order reference during migration, produce a reconciliation report, and hand off to the customer's admin to create corresponding Dolibarr Invoices. The Work Order billing sub-system in CLEAR does not map to a live Dolibarr object and must be entered manually or through a follow-on invoice-migration engagement.
| CLEAR Media ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Productions | Projects1:1 | Fully supported | |
| Dailies | Projects (custom fields)1:1 | Mapping required | |
| Assets | Products (with document link)1:1 | Mapping required | |
| Work Orders | Tasks1:many | Mapping required | |
| Users | Users1:1 | Mapping required | |
| Customers / Vendors | Third Parties1:many | Mapping required | |
| Items | Products1:1 | Mapping required | |
| Documents | Documents (linked to Projects/Tasks)1:1 | Mapping required | |
| Approvals / Sign-offs | Custom fields or Notes on Projects/Taskslossy | Mapping required | |
| Chart of Accounts | Not applicable1:1 | Not supported | |
| Bank / Cash Accounts | Not applicable1:1 | Not supported | |
| Work Order billing amounts | Invoices (manual post-migration)lossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
CLEAR Media ERP gotchas
No publicly documented API for self-served exports
Mobile app login failures block access to source data
DAX branding and product naming create confusion about what CLEAR actually stores
Work Order billing sub-system is not independently accessible
Asset file references point to cloud storage, not the files themselves
Dolibarr ERP gotchas
Foreign key constraint errors on cross-distribution database restore
SQL injection vulnerabilities in version 9.0.1
Custom fields stored as JSON in extraoptions require field-by-field deserialization
Decimal precision and rounding configuration affects price fields
No native iOS/Android app forces reliance on browser
Pair-specific challenges
Migration approach
Scoping and access confirmation
We audit the CLEAR instance via the DAX web UI to identify Productions, Work Orders, Assets, Dailies, Users, Customers, Vendors, Items, and Documents. We confirm login method (web UI vs mobile app — mobile login failures are common and we default to web UI extraction), estimate record counts per object, and agree on the data-freeze window. We also confirm which Dolibarr modules are active in the destination instance so we can scope custom field activation accordingly. The scoping output is a written migration specification with object counts, mapping rules, and a risk register covering the scraping dependency.
Session-based extraction from DAX web UI
We build and validate a session-based scraper against the DAX web UI. The scraper navigates to each object list view, extracts structured records (name, type, dates, status, metadata), and handles pagination. We run the scraper in a test environment against a subset of records (typically the 10 most recent Productions) to validate field coverage and identify any UI elements that break the extraction. We add UI-diff detection to flag when the DAX interface has changed between the test run and the production extraction. Results are written to a staging CSV format that feeds the transformation pipeline.
Transformation and schema mapping
We transform the extracted DAX records into Dolibarr-compatible CSV format. Productions become Projects; Work Orders become Tasks linked to Projects; Assets become Products with document attachments; Customers and Vendors become Third Parties with correct contact types; Users map by email. We create custom fields in Dolibarr for media metadata (resolution, codec, frame rate, timecode) using the Extra Fields module. We run field-level validation against the Dolibarr schema to identify missing required fields, type mismatches, and orphaned foreign keys before any import attempt.
Dolibarr schema preparation and custom field activation
We activate the required Dolibarr modules in the destination instance: Projects (for Productions), Tasks, Products (for Assets and Items), Third Parties (for Customers and Vendors), Users, Documents, and Extra Fields. We create the custom fields for media metadata per the agreed taxonomy. We configure Third Party categories to separate Customers from Suppliers. We validate that the Dolibarr database character set supports all source field values (particularly non-ASCII characters in entity names and project titles) before the import phase begins.
Staging import and reconciliation
We run a full import into a Dolibarr staging instance using production-like record volumes. The customer's team reconciles record counts (Productions in, Projects in; Work Orders in, Tasks in; Assets in, Products in; Users in, Users in; Customers in, Third Parties in), spot-checks 25-50 random records against the CLEAR source, and validates that linked records (Tasks under Projects, Products attached to Tasks) resolve correctly. Any mapping corrections happen in staging. Work Order billing amounts are reconciled against a manually produced invoice draft for the customer's admin to review.
Production import, cutover, and billing handoff
We run the production import in dependency order: Users first (validated against the destination User table), then Third Parties, then Projects, then Tasks, then Products with document attachments, then Documents. We freeze CLEAR writes during the cutover window and run a final delta extraction for any records modified during migration. We deliver a Work Order billing reconciliation report to the customer's admin for post-migration invoice entry. We do not configure Dolibarr automations, workflows, or report templates as these are separate from data migration. We support a five-day hypercare window for reconciliation issues.
Platform deep dives
CLEAR Media ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 of 8 objects need a manual workaround.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across CLEAR Media ERP and Dolibarr ERP.
Object compatibility
1 of 8 objects need a manual workaround.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
CLEAR Media ERP: Not publicly documented.
Data volume sensitivity
CLEAR Media ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during CLEAR Media ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your CLEAR Media ERP to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave CLEAR Media ERP
Other ways to arrive at Dolibarr ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.