Migrate from Copyl to Epicor Prophet 21

Every distinct custom object type in the Copyl workspace is enumerated during scoping. We classify each entity by its dominant data pattern: entities representing manufactured items map to Epicor Part; entities representing production orders map to Epicor Job; entities representing customer-facing deliverables map to Epicor Quote. Entities that do not fit a standard Epicor table are mapped to UD (user-defined) tables on the closest standard object, with UD column names derived from the original Copyl field API names.

Copyl field definitions (field name, data type, required flag, picklist options) are translated to Epicor UD column definitions on the target table. Epicor Kinetic uses UD fields prefixed with a character (e.g., Character01, ShortChar01, Number01) with extended UD column maps to store the human-readable label. We pre-create all UD fields via the Epicor REST API or change set before any record import begins. Field types are mapped: Copyl text to ShortChar or Character, Copyl number to Number or Integer, Copyl date to Date, Copyl boolean to Checkbox.

Copyl Tasks map to Epicor Job Operations (JobOper) within a parent Job (JobHead) when the task represents a manufacturing step, or to Epicor Task records (PMTask or MultiJob) when the task represents an administrative or maintenance activity. The Copyl task title becomes the JobOper description; the assigned resource maps to the Epicor Resource Group or Labor code. Task status (custom Copyl values) is mapped to Epicor Job status codes explicitly during scoping.

Copyl Resources (people, equipment, budgets) map to Epicor ResourceGroup for equipment resources and Labor for personnel resources. The resource allocation mapping from Copyl (which resource is assigned to which task and at what capacity) is reconstructed as Epicor LaborDtl entries with labor hours and pay rates if the destination is Kinetic with Labor tracking enabled.

Copyl Projects map to Epicor Job when the project represents a manufacturing production order, or to SalesOrder when it represents a make-to-order sales contract. The mapping decision is made during scoping based on whether the project has Bill of Materials and routing dependencies. Project-level custom fields from Copyl migrate as UD fields on the target Job or Order header.

Copyl workspace users map to Epicor Employee records (linked to the User account). Role and permission data from Copyl is not migrated as access control rules because Epicor's security model (User Profiles and Permission Sets) is administered separately. We export user identities and map them by email to the Epicor Employee table.

Copyl comments attached to Tasks or Projects migrate to Epicor text note records on the corresponding parent object. Comments on manufacturing tasks attach to JobHeadText or JobOperText; comments on sales deliverables attach to OrderHedText. Comment author and timestamp are preserved in the Epicor text record metadata if the target table supports it, otherwise in a UD field.

Files attached to Copyl Tasks or Projects migrate to Epicor Document Management (DocumentRev, DocumentType) if the Epicor tenant has Document Control enabled. For tenants without Document Control, we deliver attachments as a file inventory with the target Job number or Part number cross-referenced so the customer's admin can re-attach manually post-migration.

Copyl allows arbitrary status values on any object. Epicor enforces fixed status picklists on Job (JobHead.JobClosed, JobHead.JobComplete) and other manufacturing tables. We collect every distinct status value during scoping, map each to the nearest Epicor status code or UD code, and store unmapped values in a UD field for admin review. Customers must confirm these mappings before transformation begins.

If the Copyl workspace models multi-level product structures as custom objects or linked records, those structures map to Epicor JobMtl (Job Material) records. We reconstruct the parent-component relationship using the Copyl entity references and create JobMtl records under the corresponding JobHead. Material quantity and scrap percent are mapped from the Copyl numeric fields.

If the Copyl workspace tracks external vendors or suppliers as custom objects, those map to Epicor Supplier records. The Supplier.Address fields and payment terms migrate from Copyl address and custom fields. Epicor Supplier records are required for Purchase Order generation and MRP supply planning.

If the Copyl workspace tracks inventory quantities or stock levels as custom objects, those map to Epicor PartLot (lot-controlled inventory) or PartBin (bin-controlled inventory) records. We resolve the Part number reference first, then create the corresponding lot or bin records with quantity on hand from the Copyl data.