Migrate from Upvise to Pipedrive

Upvise People map directly to Pipedrive Person records. Each Person requires at minimum a name or email to create. If Upvise Person has no email, we generate a placeholder flag field and surface it for your team to complete post-migration.

Upvise Company maps 1:1 to Pipedrive Organization. Company addresses, phone, website, and industry fields translate to Organization fields with standard value mapping. Parent-company hierarchies in Upvise map to Organization.parent_id in Pipedrive.

Upvise Jobs are the core migration decision point: each Job becomes a Pipedrive Deal, but you choose whether to create one Deal per Job (preserving granular job history) or consolidate all Jobs for a Company into a single Deal (simpler Pipedrive view). We surface this choice in the pre-migration plan and apply your rule across the full dataset.

Upvise job status values require explicit value-by-value mapping to Pipedrive stage names in your target pipeline. 'New' typically maps to the first stage, 'In Progress' to a mid-stage, 'Completed' to Won. We preserve original status-change timestamps as custom datetime fields for reporting continuity.

Upvise job owner resolves to a Pipedrive user by email match. If the Upvise owner email has no corresponding Pipedrive user, we flag the record and assign it to a fallback Pipedrive user you designate — no deal lands without an owner.

Upvise Projects contain multiple Jobs. We translate each Project to a Pipedrive Deal and attach all child Jobs as Activity records or sub-Deals linked to the parent Deal, depending on your chosen consolidation strategy. We document the exact structure in the pre-migration plan.

Upvise Assets have no direct Pipedrive equivalent. We offer two approaches: store asset data as a JSON custom field on the linked Organization, or create Pipedrive Products for tracked assets with custom fields for serial number, location, and status. Choice depends on whether you need asset records searchable as separate Pipedrive entities.

Upvise custom fields on Jobs map to Pipedrive Deal custom fields. Pipedrive auto-generates a hash-key for each custom field via POST /dealFields. We capture the hash-key during setup and write it into our migration mapping table so field values land in the correct Pipedrive column during the bulk load.

Upvise custom fields on People map to Pipedrive Person custom fields via POST /personFields. Field types (text, number, date, picklist) are preserved. Picklist fields require a value-mapping step if Upvise uses custom picklist options not present in your target Pipedrive account.

Upvise notes attached to Jobs or People migrate as Pipedrive Notes linked to the corresponding Person, Organization, or Deal record. Original note timestamps and creating-user references are preserved as metadata fields on the Pipedrive Note.

Upvise Invoices and Quotes have no Pipedrive native equivalent — Pipedrive's Smart Docs feature handles documents but requires separate setup. We migrate invoice amounts, status, and line items as Deal custom fields and create a Note summarizing the invoice content. Pipedrive Smart Docs must be configured separately to generate new quotes post-migration.

Upvise workflows (triggers on job status, field updates, or user assignments) do not migrate. We export your workflow definitions as a structured reference document so your Pipedrive admin can rebuild equivalent automations in Pipedrive's Automation builder. Workflow logic is migration-scope only on request.