Migrate from Olqan to Freshsales

Olqan Contact records map directly to Freshsales Contact. Standard fields (name, email, phone, company association, lifecycle stage, owner) transfer to Freshsales Contact properties. We preserve Olqan's lifecycle stage as a custom property on the Freshsales Contact to maintain segmentation for reporting. Email serves as the unique identifier for deduplication. Owner assignment resolves by matching Olqan owner email to Freshsales user email; unmatched owners are flagged for manual reassignment before production load.

Olqan Company records map to Freshsales Account. Company name, address, industry, size, and association records transfer to the corresponding Account properties. Olqan's company domain stored as a contact field becomes the Account Website property. We create Accounts before Contact imports so that AccountId lookup is satisfied at the moment of Contact insert, preventing orphaned Contact records with no Account association.

Olqan Deal records map to Freshsales Deal. Deal name, value, stage, associated Contact, associated Company, owner, and creation date transfer to the corresponding Freshsales Deal properties. Olqan pipeline stage names vary by organization; we capture the current stage label and probability percentage as custom fields on the Freshsales Deal so that historical stage context is preserved. Owner resolution follows the same email-match approach used for Contacts.

Olqan Projects do not have a native equivalent in Freshsales CRM. We migrate the project record as a Freshsales Custom Object with fields for project name, status, description, start date, and end date. Task hierarchy within the project is preserved by linking project-specific Tasks to the Custom Object parent record via a lookup relationship. Milestone and time log associations are recorded as notes in the custom object description field for admin reference during post-migration rebuild.

Olqan Tasks map to Freshsales Task records. We migrate task titles, descriptions, assignees, due dates, and status flags directly. Subtask nesting is preserved where the destination supports hierarchical task relationships. Assignee resolution uses the same email-match logic as owner reconciliation for Contacts and Deals. Tasks linked to Olqan Projects carry a reference to the migrated Custom Object parent.

Olqan Ticket records map to Freshsales Case if the destination Freshsales plan includes Service Cloud (Estate or Forest). Ticket customer association, agent assignment, status, priority, and conversation threads transfer to the corresponding Case properties. We map Olqan ticket priority (Low, Medium, High, Urgent) to Freshsales Case Priority values. Conversation threads migrate as Case Email records linked to the Case, preserving the original message content and timestamps.

Olqan Time Logs record hours, date, billable flag, and linked task or project reference. We migrate time entries as a Freshsales Custom Object with fields for hours logged, date, billable status, and linked entity reference. For customers on lower Freshsales tiers without custom object access, time log summary data is stored as Notes on the linked Contact or Deal with a formatted note body for admin reference. The customer selects the strategy during scoping based on their Freshsales plan tier.

Olqan custom fields on Contacts, Companies, Deals, and Tasks are detected during scoping, classified by data type (text, number, date, dropdown, checkbox), and mapped to Freshsales custom properties under Admin Settings. We create the corresponding custom properties in Freshsales before any data import begins, matching field labels and data types as closely as the Freshsales schema allows. Any Olqan custom fields that have no Freshsales equivalent are stored in a catch-all text property with pipe-delimited key-value pairs for manual post-migration extraction.

File attachments on Olqan Deals, Projects, Tickets, and Tasks are migrated as linked files in Freshsales. We preserve the original filename, upload date, and association to the parent record. Attachments exceeding Freshsales' per-file size limit are chunked and re-assembled at the destination. Large attachment volumes may extend the migration timeline and are flagged during scoping if the total attachment size exceeds 10 GB.