Migrate from Referrizer to Nutshell

Referrizer Contact records map to Nutshell Person. Name, phone, email, address, and custom field properties migrate directly. The Referrizer contact ID is preserved in a custom text field referrizer_id__c on the Person record for reconciliation. Any labels or tags on the Referrizer contact migrate as Nutshell tags. Contacts with no email or phone are migrated as partial records with a flag so the admin can complete them post-migration.

Referrizer Company records (when the business model uses them alongside contacts) map to Nutshell Company. The Referrizer company name becomes the Company name, domain becomes the Website field, and industry and employee count become custom fields if those exist in the Referrizer schema. Company records are created before Person records so that the Company lookup is satisfied at Person import time.

Referrizer Pipeline stages map to Nutshell Leads based on a lead-status rule defined during scoping. If the Referrizer contact has been through a pipeline stage, the corresponding Nutshell Lead is created with the stage name preserved. Unqualified Referrizer contacts with no pipeline history map directly to Nutshell People without a corresponding Lead record.

Referrizer Deals map to Nutshell Deals with deal name, value, stage, close date, and owner preserved. Referrizer pipeline names and stage order migrate as Nutshell pipeline and stage configuration. If the customer uses multiple Referrizer pipelines, each becomes a separate Nutshell pipeline with its own stage order. Deal associations to contacts resolve via the referrizer_id__c lookup field at migration time.

Referrizer contact-level custom fields (key-value properties) map to Nutshell Person custom fields. Nutshell supports Text, Long Text, Currency, Date, Number, and Dropdown field types. We enumerate the Referrizer custom field schema via GET /contacts before migration and match each field to the appropriate Nutshell field type. Fields without a matching type are remapped to Text. Multi-select or checkbox properties in Referrizer map to Dropdown or Text in Nutshell depending on cardinality.

Referrizer Campaign records (Regular and Automated types) do not have a direct Nutshell equivalent because Nutshell does not include campaign management as a core CRM feature. Campaign names, types, and status are preserved as Nutshell Task records or Activity Log entries attached to the relevant Person or Company, with a campaign_type__c tag to distinguish them from standard sales tasks. The campaign association to contacts is preserved by linking the same task to all relevant Person records.

Referrizer contact activity feed events including UTM tracking data, campaign opens, and link clicks migrate as Nutshell Task records with timestamps preserved. Call, email, and meeting engagements that are accessible via the Referrizer API migrate as Nutshell Tasks with activity type noted in a custom field. Smart Inbox message history is not accessible via API and cannot be migrated (documented in gotchas). We flag this gap during scoping and confirm with the customer before extraction begins.

Referrizer stores loyalty point balances as numeric custom fields on contact records rather than as a dedicated object. We separate these fields from standard contact properties during transformation and create a corresponding custom Number field in Nutshell for each loyalty balance field encountered. If the customer uses multiple loyalty programs, each point balance maps to a named custom field (e.g., loyalty_points_bronze__c, loyalty_points_gold__c). Nutshell has no native loyalty object; this is the closest structural equivalent.

Referrizer Offers (promotional codes, reward structures, referral link associations) are mapped to Nutshell as either Note records attached to the relevant Person or Deal, or as custom Text fields on the Person record if the offer is tied to a specific contact. The mapping type is chosen during scoping based on whether the customer uses Offers as standalone promotional entities or as contact-specific referral records. We preserve offer codes, reward types, and referral status in the note or field text.

Referrizer review request history (which contacts received requests, when, and to which platform) is stored as activity on the contact object. We export this as a structured note or as a custom multi-line text field on the Person record, noting the platform (Google, Yelp, Facebook), request date, and request status. Nutshell has no native review management module; this data migrates as a record of past activity rather than an actionable feature.

Referrizer contact labels and segments export as tag arrays on each contact and remap to Nutshell Tags on the Person record. Nutshell Tags are applied at the Person level and can be used for filtering and list building. If the customer uses label hierarchies or nested segments, these are flattened into a single tag string with the hierarchy indicated by a delimiter (e.g., VIP > Fitness > Monthly). The customer decides delimiter convention during scoping.

Referrizer team member records (name and email) export to map owner assignments on contacts, companies, deals, and campaigns. We match Referrizer owners by email against the Nutshell destination User table. Any Referrizer owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision the User account before record import resumes. Role-based permission structures in Referrizer do not migrate because Nutshell uses its own role model.