Migrate from CLEAR Media ERP to Infor CloudSuite Corporate

CLEAR Productions are top-level containers carrying name, type (feature, series, commercial), and a date range. We map them 1:1 to Infor Projects, using Production name as Project description and the production type as a custom Project classification field. Infor Projects serve as containers for Work Orders and Item transactions in the destination; we confirm whether Infor's Project type is active in the customer's licensed CloudSuite edition before migration.

CLEAR Dailies records link to a Production, shoot date, and a set of Asset versions. Each Dailies master record becomes an Infor Item record, with shoot date mapped to a custom date field. Individual Asset versions within a Dailies record map to separate Item variants or Infor Item Notes entries, preserving the relationship back to the parent Production through the Project reference.

Assets cover cuts, playlists, masters, and proxy files with rich metadata including format, resolution, and transcoding status. We map the CLEAR asset type taxonomy to Infor Item records, with format and resolution as descriptive fields. Asset status (active, archived, in-review) maps to an Infor Item User Defined Field. We preserve CLEAR's asset URL references to cloud storage rather than transferring raw media bytes; these are stored as external reference fields in Infor Item records.

CLEAR Work Orders link human tasks and machine-enabled tasks to Assets and Productions, carrying assignees, due dates, and financial values. We map them 1:1 to Infor Work Order records, resolving the assignee email to an Infor User record through the User mapping. Work Order status maps to Infor Work Order status codes. Any financial billed amount from CLEAR is written as a Work Order description note; it does not create an independent invoice record because CLEAR's financial sub-system is not independently accessible.

CLEAR Users (internal staff and external collaborators) have email, display name, and role fields that transfer cleanly to Infor Users. Permissions and access scopes are destination-specific and we map them to the closest Infor role configuration available in the customer's CloudSuite edition. Any CLEAR User without a matching Infor User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

CLEAR entity records for production clients map to Infor Business Partners with type Customer. We map company name to Business Partner name, address fields to Infor address records, and contact name to the Business Partner contact role. Billing-specific fields not present in the CLEAR source record are omitted and flagged for manual entry in Infor.

CLEAR entity records for third-party service vendors map to Infor Business Partners with type Supplier. We follow the same mapping pattern as Customer records: company name to Business Partner name, address fields to Infor address records, and contact name to a Business Partner contact role. Tax identifiers from CLEAR vendor records map to Infor Business Partner tax fields where present.

CLEAR Items represent deliverables, equipment, or services tracked for billing within a Production. We map Items to Infor Items, preserving unit cost and description fields. Custom fields on CLEAR Items map to Infor User Defined Fields on the Item record. Item type (deliverable, equipment, service) maps to an Infor Item classification field to preserve the business distinction.

Documents in CLEAR (contracts, briefs, approval sign-off sheets) attached to Productions or Work Orders are extracted as metadata records: name, type, date, owner. We map them to Infor Document Management (IDM) records linked to the corresponding Project or Work Order. Document content (PDFs, spreadsheets) is not migrated as binary blobs through the standard migration scope; we flag these for manual upload or a separate document transfer engagement.

Approval records in CLEAR exist as status flags on Dailies and Assets with an approval chain (approver, timestamp, decision). We extract the approval chain as structured metadata fields on the parent record rather than a standalone object. In Infor CloudSuite, approval workflows are configured per document or transaction type. We flag which Infor approval workflows need to be configured to reproduce the original CLEAR approval chain and deliver the configuration inventory to the customer's admin team.

CLEAR does not expose a general-purpose Chart of Accounts as a standalone data object. Financial ledgers are managed within the Work Order billing sub-system and are not independently exportable. We do not attempt to migrate a Chart of Accounts from CLEAR. Any financial values carried in Work Orders are transferred as descriptive text notes within the Work Order record. If the customer requires a complete chart of accounts in Infor, we recommend building it from scratch or from an alternative finance system export.

CLEAR does not expose a treasury or bank account object. Open AP/AR balances are not stored as independent records and cannot be migrated as such. We flag this as a gap in the CLEAR source data and recommend that the customer open the required bank accounts in Infor manually before go-live or from an alternative accounting system export.