Migrate from Olqan to HubSpot

Olqan client records map directly to HubSpot contacts. The primary email, phone, job title, and address fields transfer to HubSpot's standard contact properties. Olqan client status maps to a HubSpot custom property because HubSpot uses lifecycle_stage for this purpose. If Olqan tracks a client as a person (not a company), the record lands as a Contact; if it represents an organization, it routes to Company first, then the client record links as a contact under that account.

Olqan stores client progression through a status or stage field. HubSpot has no native equivalent for a single-stage progression — lifecycle_stage is the closest construct but carries marketing-contact semantics. We create a custom pick-list property (Client_Status__c) on the Contact record and preserve the exact Olqan values. If Olqan uses a standard status set, we map those to HubSpot lifecycle stages where a clear equivalent exists (e.g., Olqan 'Active Customer' → HubSpot 'customer').

Olqan organization records map to HubSpot companies. Company name, domain (website), industry, employee count, and annual revenue transfer directly. Olqan parent-company relationships map to HubSpot's Parent Company field. HubSpot's company model supports one primary contact per company; if Olqan tracks multiple client records per company, we designate one primary contact and associate the rest via HubSpot's Contact associations feature.

Olqan opportunities map to HubSpot deals. Deal name, amount, expected close date, and owner transfer directly. Olqan's pipeline stage names map to HubSpot deal stage values via value-mapping configuration before migration. HubSpot's deal record requires an associated company; Olqan opportunities without a linked company land under a default 'Unassigned' company record or get routed based on the opportunity's primary contact.

Olqan workspaces with a single default pipeline map to one HubSpot deal pipeline. If Olqan has multiple named pipelines (rare in standard Olqan), each pipeline creates a separate HubSpot deal pipeline. HubSpot's pipeline model supports stage probability, forecast category, and stage-order customization per pipeline, which we configure during the HubSpot-side setup phase before data lands.

Olqan product or service items map to HubSpot products. Name, description, price, and unit transfer directly. HubSpot products are standalone objects that attach to deals via line items. If Olqan tracks line-item detail on opportunities (product + quantity + unit price), we preserve that detail as HubSpot line items linked to the migrated deal.

Olqan task records with a subject, due date, assigned owner, and completion status map to HubSpot tasks. Original timestamps and owner assignments are preserved. HubSpot tasks attach to a contact or company record; if an Olqan task is associated with an opportunity, we link it to the primary contact on the migrated deal to maintain the association chain.

Olqan meetings with title, date, time, attendees, and outcome map to HubSpot meeting engagements. We map the Olqan meeting title to the HubSpot meeting subject and preserve the original start and end timestamps. Attendees resolve by email against migrated HubSpot contacts.

Olqan notes attached to clients, companies, or opportunities map to HubSpot notes. Rich-text formatting is preserved where possible. Notes without a clear associated contact link to the primary contact of the related opportunity's company to ensure visibility in HubSpot's timeline view.

Olqan file attachments on clients, companies, or opportunities re-upload to HubSpot Files and attach to the corresponding migrated record. Files over 25MB are flagged since HubSpot's default file size limit is 25MB per file; larger files are chunked or linked via URL if chunking is not feasible.

Olqan custom objects (Enterprise tier) map to HubSpot custom objects 1:1. Custom object associations in Olqan that use N:N relationships require HubSpot junction objects — we document the relationship structure during discovery and create the junction schema before migration. Custom object field types are mapped type-by-type: text to text, number to number, date to date, and pick-list to pick-list.

Olqan workflows, task triggers, and automation logic do not migrate. HubSpot's workflow engine operates on different triggers, conditions, and actions than Olqan's automation builder. We export your Olqan workflow definitions as a structured reference document and recommend engaging a HubSpot partner to rebuild them in HubSpot Workflows post-migration.