Migrate from Referrizer to Freshsales

Referrizer Contacts map to Freshsales Leads for records that are prospect or early-stage, and to Freshsales Contacts for records that have moved into an active pipeline or have deal associations. We inspect the Referrizer contact record's pipeline association and stage property at migration time to determine the split. All contact fields — name, phone, email, address, custom fields — transfer directly. A custom text field ref_referrizer_id__c preserves the original Referrizer contact ID for audit and reconciliation.

Referrizer does not have a dedicated Company object, but contact records often carry business name in a custom field or label. We extract business name data during extraction and create Freshsales Account records from the extracted values, then link the Contact to the Account via the Business Account lookup. If no business name exists on a contact, the contact migrates without an Account association, which the customer's admin resolves post-migration.

Referrizer Pipeline deals map directly to Freshsales Deal records. The Referrizer deal stage name maps to Freshsales Deal Status, the pipeline name maps to a Freshsales Deal Type or custom field, and the deal amount, close date, and owner transfer as-is. We create the Freshsales Deal Status values and types to match the Referrizer stage names before migration so that no stage values are rejected on import.

Referrizer pipeline stages become Freshsales Deal Status picklist values. Each Referrizer pipeline also becomes a Freshsales Deal Type, allowing the customer to maintain separate deal categorization. We enumerate all Referrizer pipeline stages during discovery, create matching status values in Freshsales Admin Settings, and validate that no deal is rejected during test migration due to unknown stage values.

Referrizer Campaigns (Regular and Automated modes) have no native equivalent in Freshsales CRM, which lacks a campaign management object at the base tier. We export campaign records with name, type, status, and associated contact IDs, then write them as Freshsales Notes with a structured body that preserves campaign type, send date, and contact count. The customer's admin receives the campaign inventory as a reference document for manual recreation in Freshsales or Freshmarketer.

Referrizer Offers and referral codes are promotional entities without a Freshsales equivalent. We export offer codes, reward structures, validity dates, and referral link associations as structured metadata, then create Freshsales Note records with the offer data in a parseable format. Any contacts associated with specific offers carry that context as a custom text field offer_codes__c rather than as a native relationship.

Referrizer stores loyalty point balances as numeric custom fields on contact records, not as a distinct object. We flag all loyalty-related custom field names during discovery, then create matching custom number fields in Freshsales Contacts (e.g., loyalty_points_balance__c) before migration. Redemption history and program tier status are not transferable as native objects; we document the program structure in a handoff note for the customer's admin to determine a manual or integration-based resolution.

Referrizer tracks review request history — which contacts received requests, when, and to which platform (Google, Yelp, Facebook) — as activity properties on contact records. We extract review request metadata and write it to Freshsales Contact custom fields (e.g., last_review_request_date__c, review_request_platform__c). The full review request log is not transferable as a native history object; it is preserved in the extraction CSV as a reference for the customer.

Referrizer contact labels map to Freshsales Contact Tags. Labels are exported as string arrays per contact and inserted as Tag records linked to each Contact. Freshsales supports multiple tags per contact, matching Referrizer's label capability. Tag names transfer verbatim; the customer renames or consolidates tags post-migration if needed.

Referrizer contact activity feed events — including campaign opens, link clicks, and UTM tracking data — export as timestamped activity records. We map these to Freshsales Task records with the activity type preserved in a custom field (e.g., activity_type__c), the original timestamp as ActivityDate, and the contact linked via the WhoId. Note that Referrizer Smart Inbox message threads are not included because no API endpoint exposes that data.

Referrizer team members map to Freshsales Users by email address. We export all Referrizer users with name and email during extraction, then match against Freshsales User records in the destination. Any Referrizer owner without a matching Freshsales User is placed in a reconciliation queue for the customer's admin to provision before record import continues.

Referrizer multi-location contacts require explicit location-ID scoping during extraction to prevent cross-contamination between business locations. We scope exports by the Referrizer location account ID, then write location context to Freshsales as a custom text field (location_name__c) on the Contact or as an Account association depending on the customer's data model preference. The customer chooses the strategy during scoping.