Migrate from Olqan to Twenty CRM

Olqan Contacts map to Twenty's Person object. Standard fields (name, email, phone, job title) transfer directly. The Olqan lifecycle stage property maps to a custom field on Person since Twenty uses a different stage model. We also map the contact's associated company link and owner assignment, resolving the Olqan owner email to a Twenty user record during import.

Olqan Companies map directly to Twenty's Company object. Company name, domain, industry, size, and address fields migrate as typed fields. The Company object in Twenty serves as the Account-level parent for Person records, so we create all Companies before importing Persons to satisfy the lookup dependency. Olqan company domain becomes the Website field on Twenty Company.

Olqan Deals map to Twenty's Opportunity object. Deal name, value, stage label, and probability migrate directly. Olqan's pipeline assignment maps to a Twenty pipeline configuration we set up during schema design. Closed-won and closed-lost reasons from Olqan custom fields migrate to custom fields on the Twenty Opportunity record.

Each Olqan deal pipeline and its stage values map to a Twenty pipeline with corresponding stage records. Stage probabilities migrate as percentage values. We configure the pipeline in Twenty before Deal migration begins so that stage values are valid at import time rather than defaulting to a catch-all stage.

Olqan Tasks map to Twenty's Task object. Independent tasks and tasks nested within projects both migrate as Task records, with parent-child nesting preserved as a custom parent_task_id field where Twenty's current schema supports it. Task title, description, due date, assignee, and status migrate directly. Tasks linked to specific Contacts or Deals carry the appropriate Twenty ID references resolved during the import phase.

Olqan support Tickets migrate to Twenty as Task records with a custom ticket_status field, or as a custom object depending on the customer's preference during scoping. Ticket priority, agent assignment, customer association, and conversation threads migrate. The conversation history is preserved as Task description or as a linked Note if the thread is long-form.

Olqan Employee records have no direct Twenty CRM equivalent since Twenty is CRM-focused rather than an HR platform. We create a custom Employee object in Twenty with fields for job title, department, start date, contact email, and manager hierarchy. Employee-to-Employee manager lookups resolve by email match. HR data such as payroll, leave balances, and performance reviews are out of scope for migration to Twenty's CRM model.

Olqan Projects migrate as a custom Project object in Twenty with a name, description, status, and milestone list. Individual tasks within a project link to the Project record via a custom lookup field. Time logs associated with Olqan Projects migrate as Task records with a billable flag and hours field. If the customer prefers not to carry Project data into Twenty, we flag this during scoping and exclude it from the migration scope.

Olqan Time Logs associated with tasks or projects migrate as Task records with the billable flag set and hours recorded. Time logs not linked to a task are attached to the parent Project record. Duration and date migrate as typed fields. Unbilled time entries with no project association migrate as standalone Task records for reconciliation.

Olqan Invoices migrate as a custom Invoice object in Twenty with line item data stored in a custom line_items JSON field or as related custom records. Invoice header fields (total, status, payment terms) migrate directly. Historical paid invoices retain their original amounts and dates. Since Twenty has no native invoicing module, customers seeking continued invoice generation should evaluate Twenty's custom object capabilities against their workflow needs or maintain a separate billing tool.

Olqan Users and Owners map to Twenty User records. We match by email address, which serves as the unique identifier. Any Olqan Owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Olqan users migrate as inactive Twenty users to preserve historical assignment on closed deals and completed tasks.

Olqan custom fields on Contacts, Companies, Deals, Tasks, and Tickets migrate to Twenty custom fields on the corresponding objects. We detect field data types (text, number, date, checkbox, dropdown) and map them to the equivalent Twenty field type. Custom field labels are preserved. Fields on excluded objects (HR, Finance modules) are documented in the custom field inventory but not migrated unless the customer requests a custom object for that data.