Migrate from GENIEE to Pipedrive

GENIEE SFA/CRM Contact records map directly to Pipedrive Person. Japanese field labels (e.g., 担当者名, 会社名, メールアドレス) are translated during the scoping phase using machine-assisted translation validated by a Japanese-speaking data engineer. The primary email address, phone, and owner assignment migrate as Person fields. Any missing required Pipedrive Person fields are flagged in the field mapping workbook before import.

GENIEE Account records map to Pipedrive Organization. Address fields (postal code, prefecture, city, street) from GENIEE are mapped to Pipedrive's address compound field, with Japanese regional conventions (prefecture as a picklist where available) handled during normalization. Organization is created before Person import so that the Organization-ID lookup is satisfied at the time of Person insert.

GENIEE Deal records map to Pipedrive Deal with pipeline stage names translated from Japanese and mapped to Pipedrive Stages. Win/loss probability percentages from GENIEE are preserved in custom fields on Deal since Pipedrive stage probabilities are calculated rather than stored per deal. The GENIEE deal owner maps to Pipedrive User via email match.

GENIEE configurable pipeline stages are mapped to Pipedrive Stages within the target Pipeline. Each GENIEE stage name (in Japanese) is translated to an English equivalent during scoping. Probability values per stage are stored as custom numeric fields on Deal since Pipedrive does not support per-deal probability overrides in the same way. The customer configures the Pipedrive Pipeline and Stage structure before migration.

GENIEE task engagements map to Pipedrive Activity records of type to-do. Status (open/completed), due date, priority, and subject are preserved. HubSpot-style description text migrates to the Pipedrive Activity note field. Task owner resolution uses the same email-match User lookup as other owner-bearing records.

GENIEE call engagements map to Pipedrive Activity records of type call. Call disposition, duration, and any notes migrate to custom Activity fields. The original call timestamp is preserved in the Activity start field. Call activities are linked to the parent Person and Deal via Pipedrive's deal_id and person_id on Activity.

GENIEE meeting engagements map to Pipedrive Activity records of type meeting. Meeting subject, start/end datetime, location, and attendee list migrate. Attendees are stored as additional Person notes or as separate Activity participants depending on Pipedrive plan capability. Meeting notes migrate to the Activity description field.

GENIEE email engagements map to Pipedrive Activity records of type email. Email subject, body (plain text or rich text), sender, recipient, and timestamp are preserved. Email is linked to the relevant Person and Deal. Note that Pipedrive stores email content within the Activity record; it does not maintain a separate email message object like Salesforce.

GENIEE engagement notes map to Pipedrive Note records attached to the relevant Person, Organization, or Deal via the parent object and ID. Rich text formatting is normalized to Pipedrive's supported format. Attachments on notes migrate as separate file attachments.

GENIEE SFA/CRM Users mapped as record owners migrate to Pipedrive User records. Resolution is by email match. Any GENIEE Owner without a matching Pipedrive User is placed in a reconciliation queue; the customer's admin provisions missing Pipedrive Users before record import resumes. User name, email, and role title transfer; GENIEE role permissions do not map to Pipedrive's role model and are flagged for manual rebuild.

GENIEE tenant-specific custom fields on Contacts, Accounts, and Deals are discovered during scoping, translated from Japanese labels to English, and mapped to Pipedrive custom fields. Field type conversion handles text to text, integer to integer, date to date, and multi-select picklist equivalents. Custom fields are pre-created in Pipedrive before data import so that they are available during the field mapping phase.

GENIEE DSP campaign metadata (budget, targeting parameters, ad formats, flight dates, impression and click data) does not map to any standard Pipedrive object. We export DSP campaign metadata as a structured JSON or CSV dataset and deliver it alongside the migration as a custom data package. The customer can import DSP metadata as a custom object (if on a Pipedrive plan that supports custom object API access) or use it as a reference dataset in a BI tool. DSP bid logs and real-time bid data are not migrated as they are SSP infrastructure data not suited for CRM storage.