Migrate from Referrizer to Twenty CRM

Referrizer Contacts map directly to Twenty Person records. We extract name, phone, email, custom fields, labels, and visit history via the paginated GET /contacts endpoint (100 records per page). The Person record is the primary migration target and is created first so that subsequent objects (deals, campaigns) can resolve the Person lookup by email or phone as the dedupe key.

Referrizer does not have a standalone Company object, but multi-location accounts store location-level business names that map to Twenty Company records. We extract location business names from the account structure and create Company records, then link Person records to the correct Company via the Person's companyAssociation field in Twenty. If no multi-location structure exists, we create a single Company record to hold the business name.

Referrizer Pipeline stages map to Twenty Opportunity records. Stage names, order, and any lead-to-contact associations migrate. We create Opportunity records with the stage name and link each to the corresponding Person. The Opportunity object in Twenty supports custom fields for deal value, close date, and status, which we populate from the Referrizer pipeline data.

Referrizer stores loyalty point balances as numeric custom fields on contact records rather than as a dedicated object. We identify all loyalty-related custom fields during schema enumeration, separate them from standard contact properties, and create equivalent custom number fields on the Person object in Twenty before migration. Point balance values migrate as integer or decimal values depending on the source field type.

Referrizer Campaigns (Regular and Automated modes) export as records with type, status, and contact association data. Twenty has no native campaign scheduling object, so we create a custom Campaign object via Settings → Data Model before migration and map campaign name, type, status, and created date. Campaign-contact associations migrate as linked records on the custom Campaign object. Automated campaign triggers and re-entry logic do not migrate; we document the configuration for the customer's admin to rebuild in Twenty's workflow builder.

Referrizer Offers and referral relationships export as distinct records with offer codes, reward structures, and referral link associations. We create a custom Offer object in Twenty to store offer codes and reward details, then link each Offer to the referring and referred Person records via custom lookup fields. Referral link associations are preserved as text fields on both the referring and referred Person records.

Referrizer automates review requests across Google, Yelp, and Facebook. Review request history—which contacts received requests, when, and to which platform—stores as activity on the contact object. We export this as a custom ReviewRequest object in Twenty with fields for contact (lookup to Person), platform, request date, and status. Review content itself (the actual review text) is not stored in Referrizer's API and cannot be migrated.

Referrizer custom fields are contact-level key-value properties. We enumerate all custom field names and types via GET /contacts before migration, then pre-create matching custom fields on the Person object (and Company where applicable) in Twenty via the Data Model settings. Field type mapping follows: text to TEXT, numeric to NUMBER, date to DATE, checkbox to CHECKBOX, and picklist to SELECT. We enable Advanced mode in Twenty Settings to expose API field names for import mapping.

Referrizer contact labels export as tag arrays on each contact record. We map these to Twenty's Tags feature on Person records. Tags in Twenty attach via the TagRelation object, and we create any tag values that do not already exist in the destination workspace during migration. The tag vocabulary is preserved to maintain segmentation capability in Twenty.

Referrizer tracks contact activity feed events including campaign opens, link clicks, and UTM data accessible via contact activity endpoints. We export these as Note records in Twenty linked to the corresponding Person record, with the activity type and timestamp preserved in the Note body. Activity event timestamps maintain chronological ordering for the contact timeline.

Referrizer team member records (name, email) export for owner assignment mapping. We match by email against Twenty workspace users. Any Referrizer owner without a matching Twenty user goes to a reconciliation queue for the customer to provision before record import. Role-based permission structures in Referrizer do not have a direct Twenty equivalent and are documented for manual rebuild.

Referrizer multi-location accounts scope contacts by location ID. We scope each export by location account ID to prevent cross-contamination, validate contact counts match expected location totals, then create Company records per location and set a custom location field on each Person record to preserve location association in Twenty.