Migrate from Wise Agent to Pipedrive

Wise Agent contacts map directly to Pipedrive People. Each contact's name, email, phone, address, and custom properties transfer as Person fields and custom person fields. Wise Agent's primary_company flag determines the org_id link in Pipedrive. Multi-address records are concatenated into Pipedrive's single address format with street, city, state, and zip preserved in the appropriate sub-fields. Custom properties on contacts are created as Pipedrive custom person fields before migration begins.

Wise Agent companies map to Pipedrive Organizations. Company name, domain/website, address, industry, and employee count transfer as Organization fields. Parent-child company hierarchies in Wise Agent map to the Organization parent_id field. Multi-level hierarchies are preserved in Pipedrive's parent_org_id field, and we flag any circular references for manual resolution before the migration run. Company custom properties are created as Pipedrive custom organization fields.

Wise Agent deal records and transaction checklists both map to Pipedrive Deals. Transaction checklist items, milestone dates, and status fields become custom fields on the Deal. Pipedrive has no native transaction module — this is a custom field reconstruction. We create Transaction_Status__c, Checklist_Completed__c, and milestone date fields via POST /dealFields before writing any deal data, mapping each checklist item to a boolean or date field on the associated Pipedrive Deal.

Wise Agent deal pipelines map to Pipedrive Pipelines. Each pipeline's stages transfer as Pipedrive stage entries within the pipeline. Stage order and probability values are mapped value-by-value from Wise Agent stage configuration. We retrieve the pipeline structure via GET /pipelines, create any missing pipelines in Pipedrive using POST /pipelines, and then populate stages with their respective probability percentages and names from Wise Agent.

Wise Agent stage names are mapped to Pipedrive stage names per pipeline. Stage probability percentages and forecast categories are re-applied in Pipedrive based on the destination stage configuration. Stage-entered timestamps from Wise Agent are preserved as custom datetime fields. We build a value-mapping table that pairs each Wise Agent stage ID with its corresponding Pipedrive stage_id so deal records land in the correct pipeline stage during migration.

Wise Agent labels (Buyer, Seller, Investor, etc.) have no direct Pipedrive equivalent. We map them to Pipedrive Tags for quick segmentation. For structured label sets used in reporting, we create a custom pick-list field (Label_Category__c) so the data is filterable in Pipedrive list views. Multi-value labels on a single contact become multiple Pipedrive Tags, while the custom field captures the primary label for reporting purposes.

Wise Agent drip campaigns and email autoresponders do not transfer to Pipedrive. We export the campaign definition (step order, delay intervals, content references) as a CSV rebuild reference so your Pipedrive admin can reconstruct sequences in Pipedrive Automations or the Sequences tool. The CSV includes trigger conditions, audience filters, and step-by-step sequence logic extracted from Wise Agent's campaign configuration.

Wise Agent email logs, call records, meeting notes, and freeform notes map to Pipedrive Activities (type: email, call, meeting) and Notes. Original timestamps, owner assignments, and parent-record links (person, organization, deal) are preserved during migration. Call duration and outcome fields map to Pipedrive activity duration and note content respectively, while email subjects become the activity subject field for quick reference in Pipedrive's activity feed.

Wise Agent owner records (agents on the account) are resolved by email match against Pipedrive Users. Unmatched owners are flagged before migration — the team either creates Pipedrive users for them or assigns records to a fallback owner during migration. Owner email addresses are used as the primary key for matching; if no Pipedrive user exists with that email, the record is held in a staging queue for admin resolution before the Person migration batch runs.

Wise Agent's referral tree (who referred whom) has no Pipedrive equivalent. We preserve referral relationships as a custom text field (Referred_By__c) on the Person record with the referrer's name and original Wise Agent ID for traceability. For multi-level referral chains, we create additional Referred_By fields and also add a Referral_Depth__c number field to indicate how many referral hops exist for each contact.

Wise Agent lead rules (auto-assignment, auto-tagging triggers) do not migrate. We export rule definitions as a structured document for your Pipedrive admin to rebuild as Pipedrive Automations triggered by the same conditions. The export includes rule names, trigger events, condition logic, and resulting actions so Pipedrive Automations can be configured to replicate Wise Agent's automated workflow behavior.

Wise Agent document attachments on contacts, companies, and deals re-upload to Pipedrive as file attachments on the corresponding Person, Organization, or Deal record. File size limits from Pipedrive's storage tier apply; inline images in notes are downloaded and rehosted. We preserve the original filename and upload timestamp as metadata on each Pipedrive file attachment for audit compliance.

Wise Agent custom properties on contacts, companies, and deals each require a corresponding Pipedrive custom field. We create custom fields via Pipedrive's API before migration and map values field-by-field. Pick-list custom properties require value-by-value mapping to Pipedrive's option format. Each custom property type (text, number, date, pick-list) is detected from Wise Agent's property metadata and created with the matching field type in Pipedrive.

Wise Agent calendar events and appointments map to Pipedrive Activities of type 'meeting'. Original start/end times, attendees, location, and owner are preserved. Recurring calendar patterns in Wise Agent are not reconstructed in Pipedrive — individual events migrate. Each calendar event becomes a separate Pipedrive Activity with type 'meeting', preserving the original Wise Agent event ID for reference and any location or attendee data mapped to the corresponding Pipedrive activity fields.