Migrate from OneSuite to Pipedrive

OneSuite Client records contain both individual contact details (name, email, phone, social links) and company information (company name, domain, revenue, ICP status). We split this on migration: individual contact fields map to Pipedrive Person, and company fields map to a related Pipedrive Organization linked via the Person's org_id. The OneSuite Client's revenue and ICP status migrate as custom fields on the Organization. The split is resolved using the presence of a company name field: if companyName is populated, we create both Person and Organization; if not, we create Person only.

OneSuite Leads are a distinct pipeline entity with stages, source attribution, and scoring. We assess each Lead's status during migration: unqualified leads (early pipeline stages with no associated Deal) map to Pipedrive Lead records via the Leads Inbox. Leads that have advanced to a closed or negotiation stage map directly to Pipedrive Person records. The original OneSuite lead score migrates to a custom field pipedrive_lead_score__c on the destination record. Source attribution (utm_source, utm_medium, utm_campaign) migrates as custom fields for attribution reporting.

OneSuite Projects have no native Pipedrive equivalent. We migrate Project metadata (name, status, start date, end date, total value, budget) as custom fields on a Pipedrive Deal created for each Project. The Client-to-Project relationship becomes a Deal-Organization link where the Organization is the Client's split Organization record. Project tasks and milestones are not migrated as structured records; they are summarized as a Note attached to the Deal. Projects without an associated Client are linked to a placeholder Organization record.

OneSuite Invoices reference Clients and contain line items, tax rates, payment status, and currency. Pipedrive has no native invoicing object on the Essential, Advanced, or Professional tiers; invoicing requires the separate Payments product or a third-party integration. We migrate invoice data (total amount, currency, status, line-item summary) as custom fields on the related Pipedrive Deal. Complex multi-currency invoices or those with custom tax configurations are flagged for manual reconciliation. Customers needing native invoicing post-migration are directed to Pipedrive Payments or a recommended integration partner.

OneSuite Documents can attach to Clients or Projects. We migrate document metadata (name, type, URL, upload date) as Pipedrive file attachments linked to the relevant Organization or Deal. Binary file content is migrated only if the account is within its OneSuite storage tier limit (30 GB Freelancer, 60 GB Growing Agency); we pre-scan total document volume and flag any account approaching or exceeding its cap before committing binary content. If the account is over its cap, we migrate metadata and URLs only and note the gap for post-migration file transfer.

OneSuite's API returns custom fields flattened directly onto entities with their original slug as the property key (e.g., client-tier appears as clientTier on the record, not nested under a customFields object). We parse the API response and remap each slug to a Pipedrive custom field of equivalent data type, creating the destination custom fields via Pipedrive's API before migration runs. If a destination custom field does not yet exist, we flag it for creation during the pre-migration schema setup phase. All slug names are preserved in a Pipedrive custom field note for reference.

OneSuite Members are team users assigned to Projects, Clients, and Invoices. We map Members to Pipedrive User records by email match. Any Member without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision the User account before record import resumes. Owner assignments on Client, Project, and Invoice records are resolved via this User mapping and set as the OwnerId on the destination Pipedrive record.

OneSuite's Lead pipeline stages are user-defined and vary by agency. We map stage names and order directly to Pipedrive Pipeline stages. If the customer has defined custom scoring or automation rules tied to specific stages in OneSuite, we flag these in the automation inventory document and note that Pipedrive's Automation feature uses a different rule model requiring manual rebuild.

OneSuite Templates exist for Projects and Documents and store field structure and default values. We migrate template metadata (name, type, associated fields) as Pipedrive Smart Docs templates if the customer has the Smart Docs add-on enabled. Template automation logic (workflow triggers, auto-assignment, date-based renewal rules) cannot be replicated automatically; these are documented in the automation inventory for the admin to rebuild in Pipedrive Automation.

OneSuite engagement notes attached to Clients and Projects migrate as Pipedrive Notes linked via ContentDocumentLink to the parent Person, Organization, or Deal. Note timestamps are preserved by setting the Note's created date to the original OneSuite engagement timestamp. Attachments within notes migrate as separate file attachments on the same parent record.