Migrate your Referrizer data

Contacts is the core object in Referrizer, storing name, phone, email, custom fields, labels, and visit history. The API supports pagination up to 100 records per page with perPage and page parameters, and timestamps are returned in ISO 8601 UTC. We map contacts 1:1 with field-level preservation of standard properties.

Custom fields are contact-level key-value properties documented in the API. We inspect the custom field schema via GET /contacts before migration to enumerate all custom field names and types. Value mapping is required when the destination platform uses a different field type or naming convention.

Referrizer's Pipeline feature manages leads through configurable stages. The KB documents stage management under the Pipeline category. We preserve stage names, order, and any lead-to-contact associations during migration.

Campaigns exist in two modes: Regular and Automated. Automated campaigns support multiple reentries with configurable minimum time between triggers. We export campaign records with their type, status, and associated contacts, but destination platforms vary in how they represent campaign logic and reentry rules.

Offers are promotional entities that drive referral activity. Referrizer tracks referral relationships between contacts. We export offer codes, reward structures, and referral link associations as related objects tied to contacts.

Loyalty points are stored as numeric properties on contact records. We flag point balances during scoping because many destination CRMs do not have a native loyalty object — points are typically remapped to a custom number field or a loyalty app instead.

Referrizer automates review campaigns across Google, Yelp, and Facebook. Review request history (which contacts received requests, when, and to which platform) is stored as activity on the contact object. We export this as engagement history, not as a standalone review object.

Contacts can be tagged with labels for segmentation. The KB confirms label-based contact management and filtering. We export label assignments as tag arrays on each contact and remap them to the destination's tagging or segment model.

Smart Inbox conversations are ephemeral messaging threads that do not expose a documented public API endpoint. Only campaign-level sent/delivered data is accessible via the Reports API. We cannot migrate inbox message history.

Referrizer tracks contact activity feed events including UTM tracking data, campaign opens, and link clicks. This data is accessible via the contact activity endpoints. We export activity events as timeline entries on each contact.

Team members and role assignments are managed within Referrizer. We export user records including name and email to map owner assignments on contacts and campaigns, but role-based permission structures require manual reconstruction in the destination.

Referrizer supports multi-location businesses with account-level scoping. Contacts are associated with specific locations. We scope exports by location account ID to prevent cross-contamination, then reassign location ownership in the destination platform.