Migrate from Referrizer to Zoho CRM

Referrizer Contacts map directly to Zoho CRM Leads for unqualified prospects (contacts with no associated deal) and Contacts for qualified records. We preserve Referrizer custom fields as Zoho CRM custom fields scoped per module. The referrer relationship (which contact referred which) migrates as a custom lookup field on the Contact record pointing to the referring contact, or as a custom text field if the referral chain is a flat field rather than a relational one.

Referrizer contacts can be associated with a business name; if the source data includes company records or business affiliations stored as contact properties, we extract them as Zoho Accounts. Business address, phone, and website from Referrizer contact properties map to Account fields. Single-location businesses typically have no separate Company record in Referrizer; in that case we create Accounts from the business_name property on Contact.

Referrizer Pipeline stages map to Zoho CRM Deal stage names. The pipeline assignment in Referrizer (which pipeline a deal belongs to in multi-pipeline setups) maps to a Zoho custom field on Deals or a custom view filter. Closed-won and closed-lost reasons from Referrizer custom properties become Zoho custom picklist fields on the Deal.

Referrizer Regular and Automated campaigns migrate to Zoho Campaigns with campaign name, type, status, and start/end dates. Campaign type (Regular vs Automated) is preserved as a custom field. Contact associations (which contacts are enrolled in which campaign) migrate as Campaign Member records linking each Contact to the Campaign. We do not migrate automated campaign logic (re-entry rules, minimum time between triggers) because those are automation configurations rather than data.

Referrizer Offers (promotional entities with offer codes, reward structures, and referral link associations) have no direct Zoho CRM standard equivalent. We create a custom Deals- or Contacts-related module called Offers with fields for offer code, reward type (points, discount, free service), reward value, and referral link URL. Offer codes linked to specific contacts migrate as custom lookup fields on the Contact pointing to the Offer record.

Referrizer loyalty point balances are stored as numeric custom fields on Contact records, not as a distinct object. We separate these fields from standard contact properties during transform and remap them to a Zoho CRM custom number field named Loyalty_Points__c on the Contact module. If the customer licenses Zoho FSM, we create a separate Loyalty module with a relational lookup to Contact and fields for point balance, tier, and last redemption date.

Referrizer contact labels (used for segmentation across locations, customer type, or campaign cohort) migrate to Zoho Tags on Contact records. Multi-label assignments on a single contact become multiple Tag records linked to that Contact. Tags in Zoho are module-scoped, so Referrizer contact labels become Contact-level Tags and do not automatically apply to Deals or Accounts unless the customer requests cross-module tagging.

Referrizer review request history (which contacts received review requests, when, and to which platform: Google, Yelp, or Facebook) is stored as activity on the Contact object. We extract these as a custom module called Review_Requests__c with fields for Contact lookup, request date, target platform, request status (sent, opened, reviewed), and the review URL if available. Review request activity history is preserved as a chronological record rather than a live sync.

Referrizer contact activity feed events (campaign opens, link clicks, UTM tracking data) migrate to Zoho Tasks with activity type recorded in a custom picklist field and the original timestamp preserved as Activity Date. If the source includes call or meeting engagement records, these map to Zoho Tasks with subtype = Call or Events respectively. UTM parameters from Referrizer activity records migrate as custom text fields on the Task for attribution reporting.

Referrizer team members and their role assignments migrate to Zoho Users. We match by email address. Role-based permission structures (admin vs manager vs staff) in Referrizer map to Zoho Roles and Profiles, but Referrizer's permission model and Zoho's are structurally different, so the mapping is directional rather than equivalency. Inactive Referrizer users map to Zoho Users with active = false unless the customer specifies otherwise.

Referrizer multi-location accounts require location-ID scoping during extraction to prevent cross-contamination of contacts between locations. In Zoho, location separation can be achieved via a custom picklist field on Contact (Location__c), a custom module for Locations linked via Lookup, or by provisioning separate Zoho CRM organizations if strict data isolation is required. The customer chooses the model during scoping based on their reporting and access-control needs.

Referrizer Smart Inbox conversations are not accessible via the documented public API. Only campaign-level sent/delivered/open metrics are available. We cannot migrate inbox message history programmatically. During scoping we confirm with the customer whether inbox data is critical and document that it will be silently lost unless manually exported from the Referrizer UI before the migration window.