ERP migration

Migrate from CLEAR Media ERP to Dolibarr ERP

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 logo

CLEAR Media ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

67%

8 of 12

objects map 1:1 between CLEAR Media ERP and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

CLEAR Media ERP logo

CLEAR Media ERP

What's pushing teams away

  • Multiple App Store reviewers report being unable to log in at all, and the support line goes unanswered—studios using CLEAR have no recourse when the platform breaks down during production.
  • The mobile app carries a 2.4/5 rating on the Apple App Store with repeated complaints about authentication failures, forcing users to the web platform mid-shoot.
  • Studios migrating to another production-management system find no documented public API, making self-served data export difficult without Prime Focus Technologies involvement.
  • Customers report that CLEAR's feature scope is tightly coupled to the DAX dailies ecosystem, making it hard to use for non-dailies-driven workflows like episodic series tracking.
  • Organisations that outgrow CLEAR's financial module find that Work Order billing and AP/AR live in a closed sub-system with no open export path.

Choosing

Dolibarr ERP logo

Dolibarr ERP

What's pulling them in

  • Free open-source core with no per-user license fee makes it the lowest-cost entry point for small teams needing ERP and CRM in one package.
  • Self-hosted deployment gives full data ownership and eliminates vendor lock-in, especially attractive to businesses with compliance requirements.
  • Modular architecture means teams enable only the features they use, keeping the interface uncluttered and reducing learning curve.
  • Fast installation with no technical knowledge required — one reviewer set up multiple businesses in minutes using their own hosting.
  • Active community forum and marketplace of third-party add-ons provide support and extension options without mandatory subscription costs.

Object mapping

How CLEAR Media ERP objects map to Dolibarr ERP

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

maps to

Dolibarr ERP

Projects

1:1
Fully supported

CLEAR 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

maps to

Dolibarr ERP

Projects (custom fields)

1:1
Mapping required

CLEAR 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

maps to

Dolibarr ERP

Products (with document link)

1:1
Mapping required

CLEAR 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

maps to

Dolibarr ERP

Tasks

1:many
Mapping required

CLEAR 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

maps to

Dolibarr ERP

Users

1:1
Mapping required

CLEAR 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

maps to

Dolibarr ERP

Third Parties

1:many
Mapping required

CLEAR 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

maps to

Dolibarr ERP

Products

1:1
Mapping required

CLEAR 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

maps to

Dolibarr ERP

Documents (linked to Projects/Tasks)

1:1
Mapping required

CLEAR 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

maps to

Dolibarr ERP

Custom fields or Notes on Projects/Tasks

lossy
Mapping required

CLEAR 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

maps to

Dolibarr ERP

Not applicable

1:1
Not supported

CLEAR 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

maps to

Dolibarr ERP

Not applicable

1:1
Not supported

CLEAR 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

maps to

Dolibarr ERP

Invoices (manual post-migration)

lossy
Fully supported

Work 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.

Gotchas + challenges

What specifically takes care here

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 logo

CLEAR Media ERP gotchas

High

No publicly documented API for self-served exports

High

Mobile app login failures block access to source data

Medium

DAX branding and product naming create confusion about what CLEAR actually stores

Medium

Work Order billing sub-system is not independently accessible

Medium

Asset file references point to cloud storage, not the files themselves

Dolibarr ERP logo

Dolibarr ERP gotchas

High

Foreign key constraint errors on cross-distribution database restore

High

SQL injection vulnerabilities in version 9.0.1

Medium

Custom fields stored as JSON in extraoptions require field-by-field deserialization

Medium

Decimal precision and rounding configuration affects price fields

Low

No native iOS/Android app forces reliance on browser

Pair-specific challenges

  • No API means data extraction depends on DAX web UI stability

    CLEAR Media ERP does not publish a developer API, OpenAPI spec, or documented bulk export endpoint. We handle this by building a session-based scraper that navigates the DAX web interface to extract structured records. This approach is fragile: any DAX UI update by Prime Focus Technologies can break field selectors, pagination, or session handling mid-extraction. We add resilience with retry logic and UI-diff detection, but studios should understand that CLEAR is a closed system and extraction reliability cannot be guaranteed to the same standard as API-driven migrations. We recommend agreeing on a data-freeze window before scraping begins to minimise the window during which UI changes could affect the export.

  • Work Order billing values have no direct Dolibarr target

    CLEAR embeds financial billing inside Work Orders rather than exposing AP/AR or Invoices as top-level objects. Billed amounts, currencies, and line-item descriptions live in a closed sub-system that we cannot independently export. During migration, we extract Work Order financial fields and produce a reconciliation report listing every Work Order with a billing value, but these must be entered as Dolibarr Invoices or billable time entries manually post-migration. We flag this gap at scoping and recommend the customer's admin prepares a Dolibarr invoice template before cutover.

  • CLEAR entity taxonomy does not map directly to Dolibarr Third Parties

    CLEAR maintains separate entity records for production clients (Customers) and third-party service vendors (Vendors). Dolibarr uses a unified Third Party object with a contact-type flag (Customer vs Supplier). We map Customers to Third Party with Customer type and Vendors to Third Party with Supplier type, but the entity classification must be set correctly during migration to preserve reporting separation. Misclassification at migration time leads to mixed reporting in Dolibarr's financial and procurement modules.

  • Media metadata fields require custom field activation in Dolibarr

    CLEAR stores rich media metadata per Asset and Dailies record — format, resolution, codec, transcoding status, camera roll number, timecode, frame rate, and color space. Dolibarr's standard Product and Project objects do not include media-specific fields. We handle this by activating the Extra Fields module in Dolibarr and creating custom fields per object during schema design, but this adds configuration scope and requires the customer to agree on the metadata taxonomy before migration. Assets with incomplete metadata mapping will land in Dolibarr with missing fields.

  • Production hierarchy flattens in Dolibarr's project structure

    CLEAR organises data hierarchically: Productions contain Work Orders, which reference Assets and Dailies. Dolibarr Projects are flatter — Tasks link to Projects but do not have a native nested context that mirrors CLEAR's parent-child structure. We map the hierarchy by linking Tasks to Projects, but the contextual grouping (Work Order belonging to a specific Production sub-unit) requires manual reconstruction in Dolibarr's task view. Customers expecting a direct visual hierarchy translation may find the Dolibarr view less granular.

Migration approach

Six steps for a successful CLEAR Media ERP to Dolibarr ERP data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

CLEAR Media ERP logo

CLEAR Media ERP

Source

Strengths

  • CLEAR is the first proven hybrid cloud Media ERP, bridging on-premise production environments with cloud storage and review tools.
  • DAX (Digital Dailies) is deeply integrated: camera originals, proxies, and review-ready files flow through the same database as task management.
  • Work Order Management co-exists with MAM on one platform, so creative and operational teams share a single source of truth.
  • The platform supports production, broadcast, and distribution use cases within the same instance.
  • CLEAR is available on iOS, Android, and web, with biometric (fingerprint) login on mobile for quick access on set.

Weaknesses

  • No publicly documented API means third-party integrations and data exports require direct engagement with Prime Focus Technologies, limiting automation options.
  • The mobile app has a poor reputation in public reviews, with multiple users reporting login failures and no response from support.
  • CLEAR is a studio-mandated tool rather than a freely chosen platform for many users, indicating adoption friction rather than genuine product satisfaction.
  • Pricing is not publicly published, requiring sales contact for any tier comparison or budget scoping.
  • ERP financial objects (Chart of Accounts, AP/AR, Bank accounts) are not exposed as independent data objects, limiting CLEAR's suitability as a standalone finance system.
Dolibarr ERP logo

Dolibarr ERP

Destination

Strengths

  • Free core software with AGPL license and no per-user mandatory fee for self-hosted deployments.
  • Modular architecture lets teams activate only needed features, keeping the interface focused and the database lean.
  • Self-hosted option provides full data sovereignty and avoids recurring SaaS subscription costs.
  • Built-in CSV/Excel import and export wizard with saved profiles simplifies recurring data operations.
  • Low-code Module Builder allows functional extensions without writing PHP code.

Weaknesses

  • No native documented REST API for programmatic bulk operations — all migrations depend on the import/export wizard or direct database access.
  • Reporting and analytics are weak without paid add-ons, and built-in charts are limited compared to modern SaaS platforms.
  • UI design is described as dated by multiple reviewers, with infrequent visual updates to the default theme.
  • Community-only support for self-hosted deployments means no SLA or guaranteed response time for issues.
  • Security vulnerabilities (CVE-2024-5314, CVE-2024-5315) in version 9.0.1 with no immediate patch reported.

Complexity grading

How hard is this migration?

Standard ERP migration. 1 of 8 objects need a manual workaround.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across CLEAR Media ERP and Dolibarr ERP.

  • Object compatibility

    B

    1 of 8 objects need a manual workaround.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    CLEAR Media ERP: Not publicly documented.

  • Data volume sensitivity

    B

    CLEAR Media ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your CLEAR Media ERP to Dolibarr ERP migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about CLEAR Media ERP to Dolibarr ERP data migrations

Answers to the questions buyers ask most during CLEAR Media ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Small migrations under 10,000 records with one Production and no custom media metadata fields land between three and five weeks. Migrations with multiple Productions, large Dailies hierarchies, Asset metadata requiring custom field design, Work Order billing reconciliation, and entity split (Vendors from Customers) move to eight to twelve weeks because of DAX scraping robustness testing, Dolibarr custom field activation, and the billing reconciliation hand-off. The CLEAR scraping dependency is the primary timeline risk; any DAX UI instability during extraction extends the schedule.

Adjacent paths

Related migrations to explore

Ready when you are

Move from CLEAR Media ERP.
Land in Dolibarr ERP, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day