Migrate from Referrizer to HubSpot

Direct map. Referrizer contacts migrate as HubSpot contacts. All standard properties (name, email, phone, address) map directly. Custom fields on the contact become HubSpot custom properties — created before migration runs so the import has a target field. The schema mapping also includes any legacy identifiers to support later reconciliation and delta imports.

Referrizer stores company data as contact properties or associations. Where a primary company is identified, it migrates as a HubSpot company. Multi-company associations in Referrizer are surfaced as HubSpot company associations after contacts land. If no primary company is present, the contact is imported without a company link and can be associated later.

Referrizer pipeline stages map to HubSpot deal stages within a configured deal pipeline. Stage names and order are preserved value-by-value. Probability and forecast category are set in HubSpot per stage after migration. Any custom stage properties such as required fields or stage-specific SLA can also be added after the migration completes.

HubSpot has no native loyalty balance field. Current loyalty point balance migrates as a custom number property (e.g., loyalty_points_balance) on the HubSpot contact. Point redemption history migrates as engagement notes if structure allows. If Referrizer provides a redemption log, we can parse it into structured engagement records for a clearer audit trail.

Tier names (Bronze, Silver, Gold, etc.) from Referrizer's loyalty program map to a HubSpot custom pick-list property. Values are mapped one-by-one. Tier-change timestamps are preserved as a custom datetime property if present in Referrizer. This allows you to segment contacts by tier in HubSpot lists and trigger nurture workflows based on tier changes.

Referrizer stores referrer-contact links as contact relationships. We reconstruct these in HubSpot using contact associations (primary) or a custom string property holding the referrer's contact ID for reference. Multi-level referral trees are flattened to direct referrer links unless a custom object structure is requested.

Referrizer campaigns (email and SMS) and automated flows do not have a direct HubSpot equivalent. The campaign definitions are not transferable via API. We export campaign structure and contact enrollment lists as CSV so HubSpot workflows can be configured using the same enrollment logic.

HubSpot has no native review aggregation object. Review star ratings and sentiment scores migrate as custom number properties on the contact. Review text and attribution are preserved as HubSpot engagement notes with original submission timestamps. These notes can be queried for reporting or used in HubSpot dashboards to visualize review trends over time.

Referrizer campaign delivery logs (sent, opened, clicked) migrate as HubSpot engagement records with the original activity timestamp and contact association. This preserves longitudinal campaign performance data for reporting continuity. If your team needs detailed open-rate charts, these engagement records can be used to build custom reports in HubSpot's analytics tools.

HubSpot does not replicate Referrizer's Smart Inbox as a native object. Inbox message threads with customers are preserved as HubSpot engagement notes on the contact record, with the original message date and direction (sent/received) tagged in the note body. This preserves the full conversation context for future reference and support escalation.

Offer redemptions and coupon codes used in Referrizer are stored as custom properties on the contact in HubSpot. Redemption count, last redemption date, and active offer codes migrate as separate custom properties. Your marketing team can use these properties to create segmentations for promotional campaigns and to track the effectiveness of specific offers.

Every Referrizer contact custom field is identified via the custom fields API endpoint. Each becomes a HubSpot custom property before migration — property type is inferred from Referrizer's field type (text, number, date, pick-list) and mapped to the equivalent HubSpot type.

Referrizer owner IDs are resolved by email match against HubSpot users. Unmatched owners are flagged before migration so the team can invite them to HubSpot or assign a fallback owner. No record lands without a valid HubSpot owner. If multiple contacts share the same owner email, they are linked to the same HubSpot user record.

Referrizer file attachments on contacts are downloaded and re-uploaded to HubSpot Files, associated back to the contact record. File size limits per HubSpot apply (25MB per file). We verify the file integrity after upload and ensure that the association links are correctly set on each contact in HubSpot.