Migrate from Olqan to Zoho CRM

Olqan Contacts migrate to Zoho Contact. We map First_Name, Last_Name, Email, Phone, Company_Association, Lifecycle_Stage (as a custom text field contact_stage__c), and Owner. Olqan's contact owner assignment resolves to Zoho Owner by email match. If Olqan uses a lead-type lifecycle stage (e.g., Prospect, Unqualified), we create a corresponding Zoho Lead and flag it for follow-up rather than converting prematurely.

Olqan Companies map to Zoho Accounts. Company name becomes Account_Name, domain becomes Website, industry maps to Industry picklist, and size maps to Employee_Size. Olqan's company address fields map to Mailing Street, City, State, PostalCode, and Country on Account. Accounts are created before Contact import so that the Account lookup relationship is satisfied at Contact insert time.

Olqan Deals migrate to Zoho Potentials. Deal name maps to Potential_Name, deal value maps to Amount, stage label maps to Stage, and expected close date maps to Closing_Date. We preserve the original Olqan pipeline stage name in a custom field deal_original_stage__c for historical reporting since Zoho's stage values may differ. Owner, Contact Name, and Account Name references resolve via email lookup.

Olqan's pipeline stage labels (which vary per organization) map to Zoho CRM Sales Stages under the relevant Pipeline. We create a Zoho Pipeline if one does not exist and configure stage names to match the Olqan labels. Stage probability percentages migrate from Olqan to Zoho Stage Probability fields.

Olqan Projects do not have a native Zoho CRM equivalent. Zoho CRM is a CRM, not a project management tool. We migrate Project records as a Zoho custom module called Projects with fields for project name, description, status, start date, end date, and owner. Tasks nested within the project migrate as Zoho Tasks linked to the Project custom module via a lookup relationship. Customers needing full project management post-migration should consider Zoho Projects as a separate licensed app.

Olqan Employee profiles include job title, department, start date, manager hierarchy, and contact details. Zoho CRM has no native HR module. We either migrate employees as Contacts with a custom field employee_id__c and department__c, or we create a Zoho custom module called Employees with the full schema. If the customer licenses Zoho People separately, employees migrate directly there. Manager hierarchy is preserved as a self-lookup relationship in the custom module. We flag the choice during scoping.

Olqan Tickets migrate to Zoho Cases. Ticket subject maps to Subject, status maps to Status, priority maps to Priority, customer association maps to Account Name lookup, and agent assignment maps to Case Owner. Conversation threads migrate as Zoho Case Comments. If the customer also licenses Zoho Desk, we recommend migrating to Zoho Desk Cases instead, which has deeper support automation.

Olqan Time Logs (hours, date, billable flag, linked entity) have no native Zoho CRM equivalent. If the customer needs time tracking, we create a Time_Log custom module in Zoho with fields for Logged_Hours, Log_Date, Billable (checkbox), and Linked_Entity. Task records in Zoho already have a planned duration field, but Olqan's time-entry approach does not map directly to it without a custom module.

Olqan Invoices include line items, totals, status, and payment terms. Zoho CRM has an Invoice module but it requires the Zoho Finance Plus bundle or Zoho Books integration for full accounting functionality. We migrate invoice header data and line items as a Zoho custom module called Invoices if the customer does not license Zoho Books. If Zoho Books is in scope, we migrate directly to Zoho Books Invoices. Historical paid invoices retain original amounts and dates.

Olqan custom fields on Contacts, Companies, Deals, Projects, and Tickets migrate to Zoho CRM custom fields on the corresponding module. We detect the field data type (text, number, date, picklist, checkbox, multi-select) and create the matching Zoho field type before migration. Custom field labels are preserved as field names. If a Zoho equivalent field type is not available (e.g., a complex Olqan formula field), we store the value in a text field and note it for the customer's admin.

Olqan Users referenced as Deal owners, Ticket agents, and Project assignees map to Zoho Users by email address match. We extract every distinct user email from Olqan's object records and cross-reference against the destination Zoho CRM User table. Any Olqan owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

File attachments on Olqan Deals, Projects, Tickets, and Tasks are extracted from the export, preserved with original file names and upload dates, and linked to the parent record in Zoho. For files exceeding Zoho's attachment size limits, we migrate them to Zoho WorkDrive and store the WorkDrive link in a custom URL field on the parent record. We use Zoho's API for bulk attachment migration with chunking and exponential backoff.