Migrate from CLEAR Media ERP to Acumatica

CLEAR Contact records map to Acumatica BusinessAccount Contact sub-records. The email address serves as the primary lookup key for de-duplication and owner resolution. Original CLEAR createdate is preserved as a custom datetime field since Acumatica sets CreatedDate at migration load time.

CLEAR Company master records map to Acumatica Customer entities. Tax registration and credit-limit data have no direct Acumatica equivalent and are stored as custom fields on the Customer DAC. CLEAR primary-company associations are preserved as the primary contact flag on the related BusinessAccount.

CLEAR MediaAsset records do not have a native Acumatica equivalent. We map them to Acumatica Non-Stock InventoryItem records, which are designed for items without warehouse tracking. Asset-level metadata (type, duration, format, resolution) migrates as custom fields on the InventoryItem DAC.

CLEAR WorkOrder structures map to Acumatica PMProject records. Project description, status, date range, and budget amounts transfer directly. The original CLEAR WorkOrder number is preserved as a custom ProjectID field since Acumatica auto-generates its own project identifiers. A value-mapping table resolves any status-code differences between the two systems.

CLEAR inventory items with stock tracking map to Acumatica Stock InventoryItem records. Item code, description, type, unit of measure, and quantity on hand transfer directly. CLEAR item category maps as a custom class field on the InventoryItem DAC. When CLEAR stores item-specific attributes like color or material composition, we create additional custom fields on the target InventoryItem record.

CLEAR user and owner records are resolved by email match to Acumatica Contact sub-records. When a CLEAR owner record has no matching Acumatica contact by email, we flag the record and assign it to a configurable fallback owner so no migrated record lands without an Acumatica owner reference.

CLEAR free-text notes and file attachments are preserved as Acumatica Note and FileAttachment records linked to the target entity. File attachments are re-uploaded to Acumatica's file storage service. Original activity timestamps and owner references are preserved for audit continuity, ensuring compliance with data-retention policies.

CLEAR Project master records map to Acumatica PMProject entities. Project name, description, manager, date range, and budget amounts transfer directly. CLEAR project status codes map to Acumatica PMProject status values through a value-mapping table defined during schema planning. This ensures status continuity across the migration.

CLEAR vendor records map to Acumatica Vendor entities. Vendor name, contact information, payment terms, and tax identification transfer directly. For vendors that also appear as CLEAR companies, we create both a Customer and a Vendor record in Acumatica and link them via the business-account cross-reference table.

CLEAR allows N:N associations between contacts and companies. Acumatica models this as a primary BusinessAccount assignment plus secondary contact relationships. We migrate the most recently modified company association as the primary and surface others as secondary contact relationships, preserving the full association graph for audit purposes.

CLEAR custom objects specific to media workflows (review sessions, asset versions, delivery specifications) do not have direct Acumatica equivalents. We map these to custom DAC extension fields or name-value-pair extension tables, surfacing them as custom fields on the target Acumatica entity. The mapping plan is delivered before migration runs.