Migrate from Copyl to Microsoft Dynamics 365 Business Central

Every custom object in the Copyl workspace is enumerated during scoping. We extract the full field schema including field type, required flag, picklist values, and relationship cardinality. Each Copyl custom object becomes a Dynamics 365 custom entity deployed via a solution with the customer's publisher prefix. Lookup relationships between custom objects map to Dynamics 365 entity relationships with the same cardinality. This phase is the longest in a Copyl migration because no two workspaces share the same schema.

Copyl Projects map to the Dynamics 365 Project entity (msdyn_project) if the destination includes Project Service Automation licensing. If not, Projects migrate as a custom entity replicating the Copyl project structure with Project Name, Description, Start Date, End Date, Status, and any custom fields. Project-level custom fields are individually mapped.

Copyl Tasks map to Dynamics 365 Project Tasks (msdyn_projecttask) within the Project entity if Project Service Automation is licensed. Otherwise, Tasks migrate as standard Dynamics 365 Task records with the WhatId pointing to the parent Project entity. Task Title, Description, Status, Priority, Due Date, and Assignee migrate directly. Custom fields on tasks map to custom Task fields in Dynamics 365.

Copyl Resources (people, equipment, budgets) map to Dynamics 365 BookableResource. Resource type (User, Contact, Equipment, Generic) maps to the BookableResourceType field. Resource allocation assignments from Copyl migrate to Project Team Member records or Resource Assignment records in PSA. We preserve allocation percentage, start date, and end date per task-resource pairing.

Copyl workspace users map to Dynamics 365 User records by email address match. User roles and permission sets from Copyl do not have a direct equivalent in Dynamics 365's role-based security model, so we map Copyl role names to the nearest Dynamics 365 Security Role (e.g., Copyl Admin maps to System Administrator; Copyl Editor maps to Sales Professional). The customer's Dynamics 365 admin confirms role assignments post-migration.

If the Copyl workspace contains a Company or Organization object (common in ERP-style Copyl builds), it maps to Dynamics 365 Account. Company Name becomes Account Name, and any address, industry, or revenue fields map to the corresponding Account fields. Account is created before any Contact or Project import so that lookups are satisfied at insert time.

Copyl Contact records (or the Contact field on tasks and projects) map to Dynamics 365 Contact. Contact Name, Email, Phone, and Address fields migrate directly. If the Copyl workspace models contacts as related to a Company object, the Contact-Account relationship is preserved via the ParentAccountId lookup. Contact roles from Copyl map to Dynamics 365 Contact Roles on related Opportunities.

Every custom field defined in Copyl migrates as a custom field on the corresponding Dynamics 365 entity. Field types are mapped: Copyl text fields become Dynamics 365 Single-Line Text or Multi-Line Text depending on length; picklist fields become Option Sets; number fields become Decimal or Whole Number; date fields become Date fields; boolean fields become Two Option fields. Option Set values are preserved as labels.

Copyl allows users to define arbitrary status values per object rather than enforcing a standard set. We enumerate all distinct status values during scoping, then map each to the nearest Dynamics 365 Status Option Set value. Status values with no direct Dynamics 365 equivalent are preserved in a custom text field (e.g., copyl_original_status__c) on the record for audit. The customer confirms mappings during the scoping call.

Files attached to tasks, projects, and custom objects in Copyl are exported with their metadata (filename, MIME type, upload date, file size) and re-uploaded to Dynamics 365 as Annotation records linked to the target entity. If the attachment count is large, we use Azure Blob Storage as an intermediate and attach via SharePoint integration configured in Dynamics 365. Attachment content (PDFs, images) migrates as-is; executables and unsupported binary types are flagged for the customer to handle manually.

Comments attached to tasks and projects in Copyl migrate as Dynamics 365 Note records (Annotation with notetype = 1). We preserve comment body, author name, timestamp, and parent entity reference. Thread ordering is maintained by setting the CreatedOn date to the original Copyl timestamp. If comments reference other Copyl records, we preserve the text reference in the comment body rather than as a live link.

Copyl resource allocations (which resource is assigned to which task, with what percentage or hours) map to Dynamics 365 Project Team Member records. We resolve the resource reference to a BookableResourceId, the task reference to an msdyn_projecttaskid, and the allocation to booking hours or percentage fields. If the destination lacks Project Service Automation, allocations are stored as custom fields on the Task entity.

Copyl no-code workflows are not migratable as code. We document every active workflow during scoping: trigger type, conditions, actions, and affected objects. This inventory is delivered as a written handoff document for the customer's Dynamics 365 admin to rebuild in Power Automate or Dynamics 365 workflows. Workflow rebuild is outside standard migration scope.