Migrate from VBOUT to Pipedrive

VBOUT Contact records map directly to Pipedrive Person. Standard fields (name, email, phone, address) migrate as typed Pipedrive fields. VBOUT contact IDs are preserved in a custom text field vbout_contact_id__c for deduplication and cross-reference. Each Person is created before any related Organization to satisfy the Person-Organization lookup if the VBOUT Contact carries a company association.

VBOUT Lead records (distinct from Contacts in VBOUT's soft CRM model) carry lead score and source attribution. Leads with a score above the customer's defined qualification threshold map to Pipedrive Person records; leads below the threshold or with no associated deal map to Pipedrive's Lead Inbox for further qualification. Lead score migrates to a custom numeric field lead_score__c on the destination record. Source attribution migrates to a Pipedrive label or custom field depending on the customer's segmentation needs.

VBOUT Contacts carrying a company association map to Pipedrive Organization records with the company name, website, and address fields preserved. Organization records are created first in the migration sequence so that the Organization ID is available for the Contact-to-Person relationship resolution. VBOUT does not have a standalone Company object separate from Contact associations, so we derive Organization records from all Contact records that carry a company_name value.

VBOUT Tags (applied to both Contact and Lead records) carry pipeline stage context, segment classifications, and owner team tags. Tags export as a flat list and are re-applied as Pipedrive Labels on the corresponding Person, Organization, or Lead record. Pipeline stage Tags encoded in VBOUT are mapped to a dedicated Label set and documented in the migration artifact so they can be converted to Pipedrive Pipeline stages post-migration if the customer rebuilds their pipeline.

VBOUT Pipeline stages are stored as Tags on Deal records rather than as a distinct schema object. We extract all distinct Tag values applied to VBOUT Deals, identify which are stage-encoding Tags based on the customer's naming convention or documented stage list, and create Pipedrive Pipeline stages with matching names and order. Stage probability percentages are requested from the customer during scoping and applied as StageProbability values on each Pipedrive Stage.

VBOUT Deal records map to Pipedrive Deal with deal title, value, currency, expected close date, and owner preserved. Stage is resolved by matching the VBOUT Deal's stage Tag against the Pipedrive Stage created in the configuration step above. Deals without a linked Person or Organization are flagged for manual association during the reconciliation pass.

VBOUT conditional, dropdown, and payment field types do not map 1:1 to Pipedrive field types. Conditional fields are decomposed to their visible field and choice logic is documented separately. Payment field metadata (transaction reference, amount) migrates as custom text and numeric fields; actual payment records do not migrate as VBOUT payment forms are stored as isolated transactional records. We create the corresponding Pipedrive custom fields before migration begins and document any field-type approximations for the customer's admin to validate.

VBOUT Smart Audiences are dynamic segmented lists based on behavioral and demographic criteria. The segmentation rules are not exportable in a portable format. We extract the audience membership (the list of Contact IDs in each Smart Audience) and re-create the segment as a Pipedrive filter view or as a Label group. The customer receives a written description of each Smart Audience's defining criteria for manual reconstruction as a Pipedrive segment if native Pipedrive Smart Lists become available.

VBOUT sent campaign history (subject line, send date, open rate, click rate) exports as structured data via API. We import this as Note records linked to the Person, or as Pipedrive Campaign records if the customer uses Pipedrive's Campaign feature. The email body content is exported as template metadata but must be manually re-built in Pipedrive's template editor or a third-party email tool integrated with Pipedrive.

VBOUT automation workflows are stored in a proprietary JSON schema tied to its trigger-action builder. No documented export format preserves the workflow logic for import into Pipedrive. We export the workflow definition as a structured JSON artifact and produce a step-by-step rebuild guide mapped to Pipedrive's workflow automation editor (available from Professional tier). The customer must manually replicate multi-step workflows; we deliver the documentation as part of the handoff package.