Migrate from Copyl to Infor CloudSuite Corporate

Copyl's user-defined custom objects are the first entity we enumerate during scoping. There is no universal Copyl export endpoint, so we work with the customer to produce a complete entity list and field definitions. Each Copyl custom object maps to either a standard Infor CloudSuite table (if a semantic equivalent exists) or a custom table created via Infor OS schema tools. Field types are matched to Infor column data types; lookup relationships between Copyl custom objects become foreign-key references in Infor tables. This is the highest-effort mapping step because the Copyl schema is unique to every customer.

Copyl tasks map to the task or operation entity relevant to the target CloudSuite edition. For manufacturing-focused CloudSuite LN deployments, Copyl tasks with project association map to Job Operations or Shop Orders. For distribution or service-oriented deployments, tasks map to the standard Task entity in Infor OS. Status values are mapped explicitly since Copyl permits arbitrary status strings and Infor enforces picklist values. The customer confirms all status mappings during the scoping call.

Copyl resources represent people, equipment, or budget allocations assigned to tasks. We export the full resource roster including allocation percentages, rates, and type classification (person, equipment, budget). These map to Infor CloudSuite Worker records, Equipment registers, or Cost Center assignments depending on the resource type. Resource allocation mappings (which resource is assigned to which task) are preserved as child records or attributes in the destination.

Copyl projects group tasks and resources into a hierarchical structure. We preserve the project name, description, start and end dates, status, and custom fields. In CloudSuite LN, projects map to the Job or Project Management module; in M3, they map to Project. Project-level custom fields require explicit field mapping to the equivalent Infor extended data structure.

Copyl workspace user accounts map to Infor CloudSuite user identities. We export user name, email, role, and permission level and map them to Infor OS or the relevant CloudSuite user management module. Inactive Copyl users can be provisioned as inactive Infor users to preserve historical assignment records without granting active login.

Copyl comments attach to tasks and projects with author, timestamp, and body text. We export comment text, author reference, and timestamp and load them as Note records or Infor Document Management entries linked to the parent task or project entity. Thread ordering is preserved by timestamp sequence during import.

Files attached to tasks and projects in Copyl are exported and re-uploaded to Infor CloudSuite's document management system. File name, size, MIME type, and upload date are preserved as metadata. The file itself is stored in Infor IDM (Infor Document Management) or the equivalent attachment store for the target CloudSuite edition.

Every Copyl workspace has custom fields on its objects. We export the full field definition set including field name, data type, required flag, and picklist options. In Infor CloudSuite, these map to user-defined fields on the equivalent standard tables or to custom attributes via Infor OS. Picklist options in Copyl that have no direct Infor equivalent are mapped explicitly, with unmapped values stored in a catch-all text field for the customer's admin to resolve post-migration.

Copyl permits nested project structures and task hierarchies. We capture the full parent-child relationship tree and reconstruct it in Infor CloudSuite using the project work breakdown structure or job numbering convention. The hierarchy depth is preserved so that reporting by project level remains accurate in the destination.

Copyl resource allocation records (which resource is assigned to which task, at what percentage, with what dates) are exported as allocation detail rows. These map to Infor CloudSuite resource plan lines or assignment records in the project or job management module. Allocation percentages and date ranges are preserved as typed fields in the destination.