Migrate from Olqan to Salesforce Sales Cloud

Olqan CRM Contacts map directly to Salesforce Contact. The standard fields (name, email, phone, company association, lifecycle stage, owner) transfer to their Salesforce equivalents. We resolve the Olqan company_id to the Salesforce AccountId via a lookup table built during the Account migration phase. Any contact without a matching Account is flagged in the reconciliation report for the admin to address before final cutover.

Olqan Companies map to Salesforce Account. The company name becomes Account Name; address, industry, and size map to standard Account fields. The domain field from Olqan populates Account Website as the dedupe key. Account is created before Contact migration so that AccountId references are satisfied at the moment of Contact insert, avoiding orphaned contact records.

Olqan Deals map to Salesforce Opportunity. The deal value and currency transfer to Amount and CurrencyIsoCode; pipeline stage label from Olqan maps to the Salesforce StageName picklist value in the target Sales Process. We create a Salesforce Record Type per Olqan pipeline during schema design so that stage values remain scoped per business line. Closed-Lost and Closed-Won dates transfer to CloseDate.

Each Olqan deal pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that defines the valid StageName values and their probability percentages. Stage probability percentages round to the nearest integer Salesforce allows. If Olqan pipeline stage names are not valid Salesforce picklist values, we create new stage entries in the target org's Sales Process before migration.

Olqan Projects migrate to Salesforce standard Project object (available with Salesforce Field Service or an AppExchange project management app) or to a custom Project__c object if the destination org has no native project license. We preserve the project name, description, start and end dates, status, and assignees. Milestone records in Olqan become Salesforce Milestones or custom milestone__c records depending on the destination schema.

Olqan Tasks nested within Projects migrate to Salesforce Task records linked to the parent Project via WhatId. Task title, description, assignee (resolved via User email match), due date, and status all transfer. Parent-child task nesting in Olqan is preserved via a custom parent_task__c lookup or by setting the Salesforce native Subtask flag. Independent Tasks outside of Projects map to standalone Salesforce Tasks without a WhatId.

Olqan Time Logs (associated with Tasks, Projects, or Employees) map to Salesforce Time Sheet and Time Sheet Entry records if the destination org has Field Service or a project app license. Otherwise, time log data migrates to a custom Time_Log__c object with fields for hours, date, billable flag, and linked entity references. The linked entity reference (task or project) resolves to the Salesforce Task or Project ID at migration time.

Olqan Employees (job title, department, start date, contact details, manager hierarchy) have no native Salesforce equivalent since Salesforce has no built-in HR module. We map Employee records to Salesforce Contact with a custom field employee_type__c set to 'Internal' to distinguish from customer Contacts. Reporting relationships and manager hierarchy preserve in the org structure as Salesforce Role Hierarchy or a custom reporting_chain__c field. If the customer licenses an AppExchange HR app post-migration, the Employee records are already in the correct object class for re-assignment.

Olqan Invoice header data (invoice number, line items, totals, status, payment terms) has no native Salesforce equivalent. We create a custom Invoice__c object with fields for invoice number, issue date, due date, total amount, status, and line item data (custom Invoice_Line_Item__c child object or a JSON blob in a long-text field depending on complexity). Historical paid invoices preserve their original amounts and dates as read-only records. If Salesforce Billing is not in scope, PDF attachments from Olqan migrate as ContentDocument records linked to the parent Invoice__c.

Olqan Tickets (customer association, agent assignment, status, priority, conversation threads) map to Salesforce Case if the destination org includes Service Cloud. Ticket pipeline maps to Case Record Type; ticket status and priority map to Case Status and Priority picklists. Conversation threads migrate as EmailMessage records linked to the Case. If Service Cloud is not licensed in the destination, tickets are mapped to a custom Ticket__c object or documented for Service Cloud activation as a separate scope.

Olqan custom fields on Contacts, Companies, Deals, Projects, Tasks, Employees, and Tickets migrate to Salesforce custom fields of equivalent data type. We detect custom field labels, API names, and data types during discovery, then pre-create the Salesforce custom field schema (including any dependencies on picklists, formulas, or validation rules) before data import. Custom field values that do not fit Salesforce's data model (e.g., complex nested arrays) store in a catch-all long-text migration_notes__c field.

Olqan Users and Owners referenced on Contacts, Companies, Deals, Projects, Tasks, and Tickets resolve by email address match against the Salesforce destination org's User table. Owners without a matching Salesforce User enter a reconciliation queue; the customer's admin provisions missing Users before record import resumes. Inactive Olqan users map to Salesforce Users with an IsActive flag set accordingly.

File attachments on Deals, Projects, Tasks, Tickets, and Invoices migrate as Salesforce ContentDocument records via ContentVersion upload. We preserve original filename, upload date, and association to the parent record via ContentDocumentLink. Attachments exceeding Salesforce's 25 MB per file limit are chunked or flagged for the customer to store externally with a link stored in Salesforce. Unsupported file types (executables, certain legacy formats) are logged and excluded from migration.

Olqan Notes (text entries on Deals, Contacts, Projects, or Tasks) migrate to Salesforce Note records linked via ContentDocumentLink to the parent record. Note body transfers as rich text; image attachments within notes migrate as separate ContentDocument records. We preserve the note creation date as the Salesforce Note CreatedDate for chronological ordering on the activity timeline.

Olqan automations, workflow rules, and cross-module automations do not migrate as code to Salesforce Flow because the automation models differ structurally. We audit every active automation in Olqan and deliver a written inventory documenting each rule's trigger, conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds automations post-migration. This inventory is delivered as part of the standard migration handoff package.