Migrate from Unim to Pipedrive

Unim Contact records map to Pipedrive Person. Standard fields (name, email, phone, address) migrate directly. Custom fields attached to the Contact ModelID are introspected at schema-discovery time and mapped to Pipedrive custom fields, which we create via the Pipedrive API before the Person import phase. Owner assignment resolves by email match against Pipedrive Users, with unresolved owners flagged for manual provisioning.

Unim Company records map to Pipedrive Organization. The domain field from Unim becomes the Organization's Website. Organization is created before Person import so that the organization_id field is available at Person insert time for linking. Custom fields on the Company model migrate as Pipedrive Organization custom fields.

Unim Activity records (calls, emails, meetings, notes) map to Pipedrive Activity objects. The activity type determines the Pipedrive ActivityType field (call, email, meeting, note). Timestamps, subject, and body transfer directly. Owner resolution uses the same email-match approach. Activity-to-record linkage (which Person or Organization the activity belongs to) is resolved via email or record ID lookup at migration time.

If the Unim deployment includes a Deal-like bespoke object, it maps to Pipedrive Deal. The Unim deal stage values map to Pipedrive Pipeline stage IDs, which we configure during destination schema setup. Pipedrive Deal requires a linked Organization or Person at creation time, so we resolve the primary contact or organization reference from Unim before inserting Deals. Custom fields on the Unim Deal model migrate as Pipedrive Deal custom fields.

Unim custom fields have a Name, ModelID, DataType, and Nullable flag. DataTypes are looked up via the valuelists endpoint before field creation. We create equivalent Pipedrive custom fields (with matching field types where possible—text, number, date, enum, multi-select) during the schema setup phase and map them to the correct Pipedrive object type (Person, Organization, Deal, or Activity). This phase is the most time-intensive part of a Unim migration because there is no template to apply.

Unim attachments are served via the Files dimension and require a separate API call per file. We extract file metadata (filename, MIME type, size) and binary blobs in a paginated pass. Files are uploaded to Pipedrive via the Files API and associated with the target record (Person, Organization, or Deal) via the item_type and item_id fields. Large attachment sets require retry logic on 429 responses and chunked upload handling.

Unim owner IDs are instance-scoped and not portable. We extract every distinct owner_id referenced on records and match by email against Pipedrive Users. Owners with no matching Pipedrive User go to a reconciliation queue for manual provisioning. We do not create Pipedrive Users via API unless explicitly scoped; user provisioning is a permissioned action that the customer's admin typically handles.

Bespoke object types defined at the Unim application level that have no Pipedrive equivalent map to either Pipedrive custom objects (if the Pipedrive plan supports them) or to Notes attached to the parent record with the bespoke data serialized as structured text. The customer chooses the strategy during scoping. Schema for custom objects is pre-created in Pipedrive before any data import.

Unim tag associations stored as linked records or array fields are preserved. We map them to Pipedrive custom fields of type multi-select picklist on the relevant object, creating the picklist options from the discovered tag values. Tags that represent segmentation logic are flagged in the migration inventory for the customer's admin to rebuild as Pipedrive filters or static lists.

If the Unim instance has a pipeline-like structure for Deals, we map it to a Pipedrive Pipeline with stages that correspond to the Unim stage values. Stage probability percentages are approximated or explicitly provided by the customer and set during Pipedrive pipeline configuration. Multiple Unim pipelines map to multiple Pipedrive pipelines with separate stage sets per pipeline.