Migrate from WORKetc to Microsoft Dynamics 365 Sales

WORKetc Contact records map to Dynamics 365 Contact. We preserve name, email, phone, address, lifecycle information, and owner assignment. If a WORKetc Contact has no parent Company, we attach it to a placeholder Account during migration to satisfy the required AccountId lookup on Contact. The original WORKetc contact ID is stored in a custom field wtc_original_id__c for audit and reconciliation.

WORKetc Company records map to Dynamics 365 Account. The Company name becomes Account Name, and domain data maps to the Website field. Companies serve as the parent entity for related Contacts, and we preserve all Company-to-Contact relationships during migration. Account is loaded before Contact so that AccountId is resolved at Contact insert time.

WORKetc Lead records map to Dynamics 365 Lead. We preserve lead status, source, and any converted-flagged records. The original lead score or qualification data migrates to a custom field. Because Dynamics 365 requires a manual Convert action to turn a Lead into a Contact attached to an Account, we flag converted Leads during migration so the customer's admin can run the standard Convert workflow post-load.

WORKetc Deals map to Dynamics 365 Opportunity. Deal stage migrates to Opportunity StageName, deal amount to Amount, and probability to a custom field since Dynamics 365 calculates probability per stage in the Sales Process. Closed-Lost and Closed-Won reasons from WORKetc custom fields become custom Loss Reason and Win Reason fields on Opportunity. Deals linked to Companies attach to the corresponding Account during migration.

Dynamics 365 Sales has no native project management entity. We create a custom Project entity in the destination Dataverse environment matching the WORKetc Project schema, or append Project Type, Stage, and progress data to Opportunity using custom fields if the customer prefers not to add a custom entity. The full Project Types and Stages configuration, including custom stage weights, is exported and stored in a custom field project_stage_config__c as JSON for admin reference. Direct mapping of weighted progress percentages is not supported in standard Dynamics 365 fields.

WORKetc Tickets map to Dynamics 365 Case if the destination includes Service Cloud or Customer Service module. Ticket status maps to Case Status, priority maps to Priority, and the linked Customer or Company resolves to the Contact or Account already migrated. Conversation threads migrate as EmailMessage records attached to the Case for full context in the customer record.

WORKetc Invoice headers and line items migrate to Dynamics 365 Invoice. Payment history and linked bank transaction records cannot be migrated as they are external financial data requiring bank reconciliation. Invoice totals, line item descriptions, quantities, and prices transfer as read-only Invoice records that the customer reconciles against the corresponding Accounts Receivable in Business Central or their accounting system post-migration.

WORKetc custom field definitions and values migrate to Dynamics 365 custom fields on the corresponding entity. We map WORKetc field types (dropdown, text, date, numeric) to equivalent Dynamics 365 field types (Option Set, Single Line of Text, Two Lines of Text, Date Only, Decimal Number). Custom field API names are preserved with the __c suffix per Dataverse convention. Field-level security and display label differences are noted in the mapping document for admin review.

WORKetc full User records map to Dynamics 365 User by email match. We resolve every owner reference on Contact, Company, Deal, and Project during migration by matching the owner's email address to the destination User table. Any WORKetc Owner without a matching Dynamics 365 User is placed in a reconciliation queue for the customer's admin to provision before record import resumes.

WORKetc Contractor Portal users are a separate identity class with limited access and potentially no standard email address or credentials. Dynamics 365 Sales has no native contractor portal concept. We map all Contractor Portal users to Contact records with a custom field is_contractor__c set to true, preserving the contractor's name, company association, and any contact details available. Role and permission scopes are documented separately for the customer's admin to implement using Dynamics 365 security roles.

WORKetc file metadata (name, type, size, created date, associated record) migrates to Dynamics 365 SharePoint Document Locations linked to the parent record (Account, Contact, Opportunity, Case). Actual file binaries are transferred to the destination SharePoint library or OneDrive for Business location, with URLs stored in the SharePoint Document Location records. File transfer depends on the destination's available SharePoint storage and is scoped during discovery.

WORKetc Knowledge Base articles and categories migrate to Dynamics 365 Knowledge Management if the Service module is available, or to custom Note records with category stored in a custom field if only Sales is licensed. Article content and metadata transfer; rich formatting and embedded media may require post-migration review for display consistency. The Knowledge Management module must be enabled and configured before migration begins.

WORKetc workflow rules and automation triggers are not exposed via API and cannot be extracted programmatically. We do not migrate them. We deliver a written inventory of every active WORKetc workflow and automation with its trigger conditions, actions, and recommended Dynamics 365 Flow equivalent so the customer's admin can rebuild them post-migration. Web forms similarly do not migrate; we recommend Dynamics 365 Marketing forms or Power Apps portals as the replacement.