Migrate from Olqan to HighLevel

Olqan Contacts map directly to GoHighLevel Contacts using email as the dedupe key. Standard fields (name, email, phone, company association) transfer to their GoHighLevel equivalents. Lifecycle stage or custom status properties from Olqan migrate to a Contact custom field that we create during schema setup. Owner assignment migrates by resolving the Olqan owner email to a GoHighLevel User.

Olqan Company records map to GoHighLevel Locations, which serve as the account-level record for multi-location or multi-division organizations. The company name, address, industry, and size fields transfer. We resolve Company-to-Contact associations after both objects are loaded to ensure the Location relationship is satisfied at insert time.

Olqan Deals map to GoHighLevel Opportunities with pipeline stage, deal value, and associated Contact or Company preserved. Stage names from Olqan are captured as custom Opportunity status values since GoHighLevel's pipeline stages are configurable per installation. Owner assignment resolves by email match to a GoHighLevel User.

Independent Tasks in Olqan migrate to GoHighLevel Tasks linked to the parent Contact or Opportunity. Olqan project-subtasks that lack a CRM parent record migrate as standalone Tasks with a custom field indicating the original Olqan project reference for later reassignment.

Olqan Tickets map to GoHighLevel Opportunities with a dedicated pipeline and stage values representing ticket status. The ticket priority, agent assignment, and conversation threads migrate to Opportunity custom fields and related Contact notes. GoHighLevel's native ticketing is oriented toward lead and sales workflows; we configure a support-oriented pipeline during migration.

Olqan Projects do not have a direct GoHighLevel equivalent. We offer two migration paths: create a GoHighLevel Custom Object (available from Starter tier) named Project that holds project name, status, dates, and description with a lookup to the associated Contact or Location; or reference the project data as a tagged note attached to the primary Contact record for lookup-only purposes. The customer chooses the path during scoping.

Olqan Employee records contain personal contact details (name, email, phone, job title, department, start date, manager hierarchy) that map to GoHighLevel Contacts with a custom Employee tag and custom fields for department, start date, and manager email. We merge employee and CRM contact records where the same email appears in both objects, preventing duplicate Contact creation.

Olqan Invoices include line items, totals, and payment status that we preserve as related records or as structured data in Opportunity custom fields. GoHighLevel does not have a native invoicing object in the CRM layer; invoices migrate as a read-only record type on Opportunity with a link to the original Olqan invoice number for audit purposes. Ongoing invoicing in GoHighLevel requires Stripe integration or a separate invoicing tool.

Olqan custom fields on Contacts, Companies, and Deals migrate to GoHighLevel Contact custom fields and Opportunity custom fields. We create the destination custom field schema in GoHighLevel before any data loads, matching Olqan field labels to GoHighLevel field API names with proper type mapping (text, number, date, dropdown, checkbox). Data type mismatches are resolved during the transform phase.

Olqan Users referenced as deal owners, task assignees, or ticket agents are matched by email to GoHighLevel Users. Any Olqan User without a matching GoHighLevel User is flagged in the reconciliation report for the customer to provision before record import resumes. Inactive Olqan users are migrated as inactive GoHighLevel Users to preserve historical assignment data.