Migrate your Olqan data

Contacts in Olqan's CRM module store standard fields: name, email, phone, company association, lifecycle stage, and owner. We map these directly to the destination CRM's Contact object, preserving all standard field values 1:1.

Companies represent business accounts linked to contacts and deals. We migrate the company name, address, industry, size, and association records. Where the destination uses Accounts, we map Companies accordingly.

Deals in Olqan track opportunity values, stages, and associated contacts or companies. Pipeline stage names vary by organization; we capture the current stage label and probability for each deal and map it to the destination pipeline stage.

Projects hold tasks, time logs, assignees, and milestones. We migrate the project record with its task hierarchy, preserving parent-child task relationships and status values.

Tasks are nested within projects or can exist independently. We migrate task titles, descriptions, assignees, due dates, and status flags. Subtask nesting is preserved where the destination supports it; otherwise we flatten and link via naming convention.

Employee profiles contain job title, department, start date, contact details, and manager hierarchy. We migrate these as HR records, preserving reporting relationships in the organizational structure.

Time entries in Olqan are associated with tasks, projects, or employees. We extract the hours, date, billable flag, and linked entity reference, mapping to the destination's time entry object or custom fields.

Invoices include line items, totals, status, and payment terms. We migrate invoice header data and line items; historical paid invoices retain their original amounts and dates. Payment history and aging data require supplemental mapping.

Support tickets store customer associations, agent assignments, status, priority, and conversation threads. We migrate ticket records with their current status and link conversations to the destination ticket object, noting that full conversation threading may require post-migration review.

Olqan supports custom fields on most objects. We detect and preserve custom field labels, data types, and values, mapping them to the destination's custom property schema or storing them in a catch-all custom field where the destination has limited support.

User accounts map to owners and assignees across CRM, project, HR, and ticket modules. We match users by email address and flag any unmatched owners for manual reassignment after migration.

File attachments on deals, projects, tickets, and tasks are migrated as linked files. We preserve the original file name, upload date, and association to the parent record. Large attachments are chunked to avoid timeout during transfer.