Migrate from Olqan to Pipedrive

Olqan Contact records map directly to Pipedrive Person. Standard fields (name, email, phone, company association) migrate to Pipedrive's name, email, phone, and org_id fields. Lifecycle stage values from Olqan migrate as a custom field olqan_lifecycle_stage__c for reporting continuity. Owner assignment resolves via email match to Pipedrive User.

Olqan Company records map to Pipedrive Organization. Company name, address, industry, size, and domain fields migrate to Pipedrive Organization fields. Organization is created before Person import so that the org_id lookup relationship is satisfied at the moment of Person insert. We use domain as the dedupe key during import to prevent duplicate Organizations.

Olqan Deal records map to Pipedrive Deal. Deal title, value, stage, owner, associated Person, and associated Organization migrate directly. Olqan's pipeline assignment maps to a Pipedrive Pipeline that we configure before migration. Stage probability values migrate from Olqan to Pipedrive stage probability, rounded to the nearest integer.

Each Olqan pipeline becomes a Pipedrive Pipeline with corresponding stage values. Stage names, probabilities, and stage order migrate from Olqan to Pipedrive stage configuration. Pipedrive enforces a maximum stage name length of 50 characters; we truncate and note any stage names that require renaming. Closed won and closed lost stages migrate with their original probability values preserved.

Olqan's multiple deal pipelines map to Pipedrive Pipelines. Each Pipedrive Pipeline gets its own stage configuration and visual board layout (Kanban or list view). If Olqan had pipeline-specific fields, those migrate as custom fields on the Pipedrive Deal object. We configure pipeline visibility per user or team during migration setup.

Olqan Task records map to Pipedrive Activity with type=Task. Task title, description, due date, assignee, and status migrate to Pipedrive Activity fields. Subtask nesting is flattened into a single task level; if the customer requires parent-child structure, we document it as a custom field pair (parent_task_id__c, child_flag__c) for admin review. Owner resolves via email match to Pipedrive User.

Olqan Ticket records (support tickets with customer association, agent assignment, status, priority, and conversation threads) do not have a direct Pipedrive equivalent. We map ticket records to Pipedrive Activities with type=Task, preserving title, status, priority, and linked Person/Organization. Conversation threads migrate as Activity notes or as attached text files. The customer should decide whether to use a separate pipeline for support tickets or to handle support via a separate helpdesk tool post-migration.

Olqan Project records map to Pipedrive Project. Project name, status, assignees, and milestones migrate to Pipedrive Project fields. Task hierarchy under the project migrates as Pipedrive Activity records linked to the Project via the project_id field. Time logs and milestones that have no direct Pipedrive equivalent become custom fields or Activity notes for admin review.

Olqan Employee profiles (job title, department, contact details, manager hierarchy) map to Pipedrive User records for internal team members who will use Pipedrive as a CRM. Employee records that represent only contacts (not CRM users) map to Pipedrive Person records instead. We resolve by email and flag any Olqan employees without a corresponding Pipedrive User for admin provisioning.

Olqan custom fields on Contacts, Companies, Deals, and Tasks migrate to Pipedrive custom fields on the corresponding object. We detect field data types and map to Pipedrive supported types: text, numeric, date, single-select picklist, multi-select picklist, boolean, and link. Multi-checkbox fields in Olqan map to Pipedrive multi-select picklists. Custom fields that cannot map (unsupported types) are stored in a catch-all olqan_raw_data__c text field on the record for manual extraction post-migration.

File attachments on Deals, Projects, and Tasks in Olqan migrate as Pipedrive Files linked to the parent record. We preserve the original file name, upload date, and association to the parent Deal, Person, Organization, or Activity. Large files are chunked for upload and verified for integrity post-transfer.

Olqan Users referenced on Contacts, Companies, Deals, Tasks, and Tickets resolve by email match to Pipedrive User records. Any Olqan User without a matching Pipedrive User goes to a reconciliation queue for admin provisioning before record import proceeds. Inactive Olqan users are mapped to inactive Pipedrive Users with their historical assignments preserved as notes.