Migrate from Referrizer to Pipedrive

Referrizer Contact records map to Pipedrive Person objects. The contact's name, phone, email, and address fields map directly to Pipedrive Person fields. Custom fields on the contact (referral source, visit count, labels, etc.) map to Pipedrive custom fields that we pre-create before migration. We enumerate all custom field names and types via the Referrizer GET /contacts endpoint during scoping and create matching Pipedrive custom fields via the Pipedrive Field API. Labels stored as arrays on contacts migrate as multi-select custom fields or tag fields in Pipedrive.

Referrizer stores loyalty point balances as numeric custom properties on contact records, not as a distinct object. During extraction we identify the loyalty field names (e.g., loyalty_points_balance) and separate them from standard contact fields. We create a custom numeric field loyalty_points__c on the Pipedrive Person object and map the source value during transformation. If Referrizer tracks tier status (Bronze, Silver, Gold) as a separate property, we create a corresponding picklist field for loyalty_tier__c.

Referrizer Pipeline stages and lead records map to Pipedrive Deals. The lead's stage name, status, and any associated value fields map to Pipedrive Deal fields (title, stage_id, value). Pipedrive Deals require either a Person, an Organization, or both as a linked record — we resolve this by creating a Pipedrive Organization for each Referrizer account or location before inserting Deals, or by linking the Deal to the Person directly if no organization relationship exists in Referrizer.

Referrizer's pipeline stage names and order migrate to Pipedrive Pipeline stages within the designated Pipeline. We create Pipedrive Pipelines via the Pipedrive Pipeline API before migration and map stage names from Referrizer to the corresponding stage_order values in Pipedrive. If the customer has multiple Referrizer pipelines (e.g., separate for different service lines), we create corresponding Pipedrive Pipelines and map Deals to the correct one based on Referrizer's pipeline assignment.

Referrizer Campaign records (both Regular and Automated modes) cannot be migrated as live automations because Pipedrive's campaign model is fundamentally different. We export campaign metadata — name, type, status, associated contact list, and trigger configuration — into a written Campaign Inventory document that lists each campaign with its setup details and a recommended Pipedrive Automation equivalent. The customer's admin rebuilds the campaign logic in Pipedrive's Automations tool using the inventory as a guide.

Referrizer Offers and referral codes are stored as promotional entities with contact associations. We export offer codes, reward structures, and referral link associations as related data. The referral code attached to a contact maps to a custom text field referral_code__c on the Pipedrive Person. Offer eligibility migrates as a custom field or note on the associated Person or Deal. The offer's reward rules (point value, discount percentage) are documented in the Campaign Inventory for manual setup in Pipedrive.

Referrizer tracks which contacts received review requests, when the request was sent, and which platform (Google, Yelp, Facebook). This data lives as activity events on the contact record. We export the review request history as timed Activity records in Pipedrive — calls with a note indicating the review platform and request date — linked to the Person. The actual review content (stars, text) is not stored in Referrizer in a migratable form and is excluded.

Referrizer contact labels (used for segmentation) export as string arrays on each contact. We map these to Pipedrive Person tags via the Pipedrive Person ID merge operation after person insertion. For labels used as meaningful segments (e.g., VIP, churned, referral_source), we also create a multi-select custom field person_segment__c to allow filtering without relying solely on tags.

Referrizer Smart Inbox conversations are not accessible via any documented public API endpoint. Only campaign-level sent/delivered/open metrics are available. We explicitly exclude Smart Inbox from migration scope and document this data loss during scoping. Customers who need conversation history must export manually from the Referrizer UI before the migration window. Pipedrive's email sync can be configured post-migration to capture future conversations natively.

Referrizer tracks contact activity feed events including UTM source data, campaign opens, link clicks, and visit history via the contact activity endpoints. We export these as Pipedrive Activity records: campaign opens and link clicks migrate as Notes attached to the Person; visit history migrates as Task-type activities with a descriptive note field. Activity timestamps are preserved in Pipedrive's ActivityDate. We handle pagination across activity events carefully since large contact databases produce high event counts.

Referrizer team member records (name and email) map to Pipedrive Users. We resolve owner assignments on contacts and campaigns by matching the Referrizer owner email to a Pipedrive User email. Any Referrizer owner without a matching Pipedrive User goes to a reconciliation queue for the customer to provision before record import resumes. Role-based permission structures from Referrizer do not map directly and are documented for manual configuration in Pipedrive's User and Teams settings.