Migrate from Olqan to Microsoft Dynamics 365 Sales

Olqan Contacts map to Microsoft Dynamics 365 Sales Contact records. We resolve the parent Account by matching Olqan's company association field against Olqan Companies, then map those to Account records created first in the migration sequence. Contact fields — name, email, phone, job title, lifecycle stage — map to their Dynamics equivalents (firstname, lastname, emailaddress1, telephone1, jobtitle, industrycode). Olqan's lifecycle stage property migrates to a custom field olqan_lifecycle_stage__c on Contact for reporting continuity.

Olqan Company records map directly to Microsoft Dynamics 365 Sales Account. The company name becomes Account Name; address fields map to address1_line1, address1_city, address1_stateorprovince, address1_postalcode, address1_country. Industry and company size map to IndustryCode and NumberOfEmployees. Account is created before Contact migration so that the AccountId lookup is resolved at insert time, preventing orphaned Contact records.

Olqan Deals map to Microsoft Dynamics 365 Sales Opportunity. Deal name becomes Opportunity Name; deal value maps to EstimatedValue; close date maps to EstimatedCloseDate. The Olqan pipeline stage name maps to a Microsoft Dynamics 365 Sales Process and StageName via a configurable mapping table created during schema design. Owner from Olqan Deal resolves to Microsoft Dynamics 365 Sales User by email match.

Each Olqan pipeline with its stage labels and probabilities translates to a Microsoft Dynamics 365 Sales Process. We create the Sales Process in the destination org before migration, configuring StageName and StageProbability for each stage. Closed-Won and Closed-Lost outcomes from Olqan map to Microsoft Dynamics 365 Sales Won - Lost statuses with the probability override applied at migration time.

Olqan Tickets migrate to Microsoft Dynamics 365 Sales Case. Ticket subject becomes Case Title; ticket status maps to Case Status; priority maps to Priority. Agent assignment resolves to Microsoft Dynamics 365 Sales User by email. Ticket conversations are stored as EmailMessage records linked to the Case, preserving the support thread timeline. If the Dynamics 365 org does not include Service Cloud licensing, Cases may not be available and Tickets migrate to custom fields on the Account or Contact instead.

Olqan Projects store tasks, time logs, assignees, and milestones with no direct Microsoft Dynamics 365 Sales equivalent. If the project tracks billable client work, we map the project record to a custom Dataverse table (Project__c) and link it to the Account. Tasks nested within the project migrate as records in a ProjectTask__c custom table linked to Project__c. If the customer does not require project tracking in Dynamics 365, we deliver the project data as a structured CSV inventory for reference.

Olqan Employee profiles (job title, department, start date, contact details, manager hierarchy) do not map to a standard Microsoft Dynamics 365 Sales object. If the destination org includes Dynamics 365 Human Resources, we migrate to the HR module. Otherwise we create a custom Dataverse table (Employee__c) with fields for each Olqan employee attribute. Reporting relationships from Olqan's manager field map to a self-referencing lookup on the custom table.

Olqan custom fields on Contact, Company, Deal, Ticket, and Project migrate to Microsoft Dynamics 365 Sales custom attributes (CustomFields or custom __c fields on the equivalent Dataverse table). We detect field type during export parsing — text, number, date, picklist, checkbox — and map to the corresponding Dataverse attribute type. Any custom field that has no valid destination in Microsoft Dynamics 365 Sales schema is documented in a Custom Fields Inventory with data type, current values, and a recommendation for a custom field or notes field placement.

Olqan user accounts across CRM, project, HR, and ticket modules map to Microsoft Dynamics 365 Sales User records. We match by email address as the unique identifier. Users without a matching Dynamics 365 User go to a reconciliation queue for the customer's admin to provision. Assignee and owner references on Deals, Tickets, and Projects resolve via this User lookup before record import proceeds.

File attachments on Olqan Deals, Projects, Tickets, and Tasks migrate as Notes (Annotation records) in Microsoft Dynamics 365 Sales , linked via objectid and objecttypecode to the parent record. We preserve the original filename, upload date, and file body. Large attachments above 5 MB are handled as SharePoint file references if the Dynamics 365 org has SharePoint integration enabled, otherwise stored as Annotation with a size warning raised during scoping.