Migrate from Referrizer to Salesforce Sales Cloud

Referrizer Contacts with referral source, lifecycle stage labels, or engagement scores map to Salesforce Lead for unqualified prospects and Contact for qualified or active customers. We compute the split using Referrizer label assignments (referral, new, returning, VIP) as the split criteria, with the customer defining the threshold during scoping. Original label assignments preserve as a custom multi-select picklist ref_labels__c on both Lead and Contact for audit and reporting continuity.

Referrizer multi-location contacts scope by location ID during extraction to prevent cross-contamination. Each distinct Referrizer location maps to a Salesforce Account representing the business location. Contact records attach to the Account corresponding to their location assignment. Location metadata (location name, address, phone) migrates to Account fields. Accounts are created before Contact import so that AccountId Lookup is satisfied at insert time.

Referrizer custom fields are contact-level key-value properties enumerated via GET /contacts before migration. We inspect the full custom field schema to capture field names, data types, and values. Text fields map to Salesforce Text fields, numeric fields to Number, date fields to Date, and checkbox fields to Checkbox. Custom field API names from Referrizer translate to Salesforce __c field names with the original label preserved in the field-level description for admin reference.

Referrizer pipeline stages map to Salesforce Sales Processes and Record Types on Opportunity. We capture all stage names, order, and any custom stage probability values during extraction and configure equivalent stage values in Salesforce before Opportunity import. Stage probability percentages round to the nearest Salesforce-allowed integer.

Referrizer campaign records (Regular and Automated modes) map to Salesforce Campaign. Campaign name, type, status, and start/end dates migrate directly. Automated campaign re-entry configuration is documented as a Salesforce Campaign Influence or Journey Builder note for the customer's admin to rebuild in Salesforce Marketing Cloud if relevant. Campaign member associations (which contacts received which campaign) migrate to CampaignMember records linked to the converted Lead or Contact.

Referrizer stores loyalty point balances as numeric custom fields on Contact records rather than as a distinct object. We flag these fields during schema enumeration, separate them from standard contact properties during transformation, and remap them to a Salesforce custom Number field loyalty_points__c on Contact (or Account if the customer prefers location-level loyalty). Point balance history is not available in Referrizer; only the current balance migrates.

Referrizer offers (promotional codes, reward structures, referral link associations) map to Salesforce Opportunity with custom fields for offer_code__c, reward_type__c, and referral_link__c if the customer uses Opportunities to track promotional campaigns. Alternatively, offers migrate to a custom Offer object with lookup to Account or Contact. The customer selects the target model during scoping based on their Salesforce data model.

Referrizer review request history (which contacts received requests, when, and to which platform) migrates as activity records or Campaign Member status entries. We export review request logs as Salesforce Campaign Members with Member Status indicating the platform (Google, Yelp, Facebook) and the request date. If the customer wants review tracking as cases, review requests map to Salesforce Case records with custom fields for platform and status.

Referrizer labels assigned to contacts (segmentation tags) migrate to Salesforce multi-select picklist fields on Contact. We capture the full label vocabulary during extraction and configure the picklist values in Salesforce before migration. If the customer uses labels for marketing segmentation, we recommend mapping to Salesforce Topics with TopicAssignment records as a scalable alternative.

Referrizer email engagement records (sent, delivered, opened, clicked) available via the Reports API migrate to Salesforce EmailMessage records linked to Tasks on the Contact timeline. Only campaign-level email metrics are accessible; individual email body content is not guaranteed. We confirm email content availability during extraction and note gaps in the reconciliation report.

Referrizer activity feed events (call recordings, meeting logs, UTM tracking, link clicks) migrate to Salesforce Task and Event records. Calls map to Task with TaskSubtype=Call and CallDurationInSeconds preserved. Meetings map to Event with StartDateTime, EndDateTime, and Location preserved. Activity timestamps migrate as ActivityDate to preserve timeline ordering.

Referrizer notes attached to contacts migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact or Account. Note body migrates as rich text with any embedded images preserved as separate ContentDocument records. Note ownership resolves by matching the Referrizer creator user to a Salesforce User by email.

Referrizer team members and role assignments map to Salesforce User records. We extract user name and email from Referrizer and resolve by email match against the destination org's User table. Any Referrizer user without a matching Salesforce User enters a reconciliation queue for the customer's admin to provision before record import resumes. Role-based permission structures do not migrate as Referrizer roles are platform-specific.

Referrizer locations (multi-location business accounts) map to Salesforce Account records with a custom field location_id__c carrying the Referrizer location identifier. Contact records scope to their parent location Account during extraction to ensure no cross-contamination. If the customer needs to track parent-company versus location separately, we recommend a separate Location__c custom object with Account lookup.