Migrate from Origo BPO to Pipedrive

Origo BPO exports client contacts with name, email, phone, and company affiliation. These map directly to Pipedrive Person records. Email serves as the unique identifier for matching and deduplication during migration. If Origo exports include duplicate email addresses, FlitStack flags and collapses them into single Person records.

Origo BPO's client company records map to Pipedrive Organizations. Company name, website, industry, and address fields translate directly. Parent-subsidiary relationships in Origo's company hierarchy map to Pipedrive's Parent Organization field. Multiple contacts from the same Origo company link to a single Organization record.

Origo BPO service requests are conceptual equivalents of Pipedrive Deals — both represent tracked engagements with a status, owner, and associated client. FlitStack transforms Origo service request status (Open, In Progress, Resolved) into Pipedrive Deal Stage values. Service request values or fees map to Pipedrive Deal Amount if numeric data exists.

Origo BPO assigns SLA tiers (Bronze, Silver, Gold, Platinum) to client engagements. Pipedrive has no native SLA field on Deals. FlitStack creates a custom pick-list field (Service_Tier__c) on the Deal object and maps Origo's tier values. If SLA data is stored at the contact level, the custom field is created on both Person and Deal.

Origo BPO assigns staff members to service requests. Pipedrive does not have a native staff assignment object — assigned staff map to Pipedrive Users by email match. If Origo staff records include email addresses, FlitStack resolves them to existing Pipedrive users or flags unmatched staff for team setup before migration.

Origo BPO stores case notes, service summaries, and client communication logs. These migrate as Pipedrive Notes attached to the corresponding Person, Organization, or Deal. Original timestamps and note authors (resolved by email match to Pipedrive Users) are preserved on each Note record.

If Origo BPO exports include email history, these map to Pipedrive Activities of type 'email'. Each Activity links to the corresponding Person or Deal. Subject, body, and sent/received timestamps are preserved. Pipedrive's email sync feature (plan-dependent) can be enabled post-migration for ongoing tracking.

Origo BPO call and meeting records from service tickets map to Pipedrive Activities. Call activities use type 'call' with duration and outcome fields; meetings use type 'meeting' with start/end timestamps. Both link to the related Person or Deal. Original staff member who logged the call is resolved as the Activity owner.

If Origo BPO maintains a list of billable services or products, these map to Pipedrive Products. Product name, price, and unit map directly. Products can then be attached to Deals via Deal Products for line-item tracking. Pipedrive's Product library supports variants and bundles on higher-tier plans.

Origo BPO exports may include custom columns for billing code, referral source, account manager, or contract renewal date. FlitStack creates corresponding custom fields in Pipedrive using the field type that best matches the data (text, number, date, pick-list). Custom fields on Person, Organization, and Deal are created via Pipedrive's field API before data loads.

Origo BPO may store client documents, service agreements, or deliverables attached to service records. These files are downloaded and re-uploaded to Pipedrive, attached to the corresponding Person, Organization, or Deal record. Pipedrive's file size limit is 50MB per file. Files without an associated record are attached to the primary Person as a fallback.