Migrate from Rizer to Pipedrive

Rizer Contacts map directly to Pipedrive Persons. Standard fields (name, email, phone, address) map to their Pipedrive equivalents. Referral source and attribution window stored on Rizer Contact migrate to a custom Pipedrive text field (referral_source__c) that we create before import. Lifecycle stage properties migrate to a custom picklist field on Person.

Rizer Companies map to Pipedrive Organizations. Industry tags and custom company properties require value-mapping to equivalent Pipedrive Organization fields. The Company domain field becomes the Organization Website field and is used as the dedupe key during import. Organization is created before Person import so the Organization-ID lookup is satisfied at insert time.

Rizer Deals map to Pipedrive Deals. Deal stage in Rizer maps to the Pipedrive Pipeline stage name. We re-create the Rizer pipeline as a Pipedrive Pipeline with stages matching the source dealstage values before migration begins. Closed-Lost and Closed-Won dates migrate to Pipedrive's close_date and the deal status.

Rize Clients (the time-tracking product) map to Pipedrive Organizations. If a Rizer account uses both Rizer Social and Rize, we perform a second export pass against the Rize product domain (rize.io) and merge Rize Clients into the same Organization records created from the Rizer Social Company export, avoiding duplicate Organization entries for the same entity.

Rize Projects are scoped for migration only if the destination Pipedrive account has the Projects add-on enabled. Without the add-on, Projects map to Pipedrive Deals tagged with a project_flag custom field and linked to the parent Client-Organization. Task breakdowns within Projects migrate as Activities on the Deal.

Rizer call logs migrate to Pipedrive Activities with type set to Call. Call duration, disposition, and recording URL (if present) transfer to custom Activity fields. Activity timestamps preserve the original Rizer creation date for timeline integrity.

Rizer email engagement history migrates to Pipedrive Activity records with type set to Email. Email content, recipient, and send timestamp migrate as Activity body and date. We link the Activity to the target Person and Organization via Pipedrive's Person-ID and Org-ID fields.

Rizer meeting engagements map to Pipedrive Activities with type set to Meeting. Meeting title, start and end time, location, and attendee list migrate to equivalent Activity fields. Attendees are resolved by email against the migrated Person records.

Rizer task engagements map to Pipedrive Activities with type set to Task. Status, priority, due date, and assignment migrate directly. HubSpot-style task ownership maps to Pipedrive Activity owner by email match against the migrated User records.

Rizer custom field descriptors on Contacts are inspected at export time for inferred data type (date stored as string, multi-select stored as delimited text, numeric stored as text). We create type-matched custom fields in Pipedrive before writing any records, preventing silent type coercion errors that occur when Pipedrive's type constraints reject mismatched values during import.

Rizer Tags applied to Contacts are flat string lists. If the destination Pipedrive account uses the Labels feature, tags migrate as Labels on Person records. If Labels are not available on the plan, tags migrate to a custom multi-select picklist field on Person that we create during migration.

Rizer Team Members (Rizer Social user accounts) and Rize Users (time-tracking user accounts) are separate user pools. We extract all unique email addresses across both products and create a unified User provisioning list for the Pipedrive destination. Role assignments (admin, manager, member) map to Pipedrive User admin flags.