Migrate from Rizer to HubSpot

Rizer contacts map directly to HubSpot contacts. First name, last name, email, phone, job title, and address fields have named HubSpot equivalents. Owner resolution happens by email match against HubSpot user email addresses. Custom fields on a Rizer contact become HubSpot custom contact properties.

Rizer tracks referral_source as a contact-level metadata field. HubSpot has no native referral-source field. We create a custom text property (Referral_Source__c) on the Contact object and migrate the value for each record. If referral_source is a pick-list in Rizer, we create it as a HubSpot option-set property instead.

Rizer companies map 1:1 to HubSpot companies. Name, domain, industry, phone, and address fields map to HubSpot's identically named company properties. Rizer's custom company fields become HubSpot custom company properties. If Rizer stores a parent-company hierarchy, the parent link maps to HubSpot's parent_company_id field.

Rizer deals (name, amount, close date, owner, stage) map to HubSpot deals. The Rizer deal stage value maps to a HubSpot deal stage within the target pipeline. If Rizer has multiple named deal pipelines, each one maps to a corresponding HubSpot deal pipeline. Stage names are mapped value-by-value before migration runs.

Rizer's pipeline concept maps to HubSpot's deal pipeline. Each Rizer pipeline becomes a HubSpot deal pipeline. Stage names within each pipeline are mapped individually to HubSpot stage names in the corresponding pipeline. We deliver the stage-value mapping table as part of the pre-migration plan so your HubSpot admin can configure the pipeline stages before data lands.

Rizer activity records — logged calls, sent emails, and notes — map to HubSpot engagements. Each activity type creates the corresponding HubSpot engagement subtype (CALL, EMAIL, NOTE). Original timestamps and owner information are preserved. The engagement is associated to the correct HubSpot contact or company record using the resolved contact/company IDs.

Rizer owner IDs resolve to HubSpot owners by email address. If a Rizer owner email has no matching HubSpot user, we flag the record before migration and you choose a fallback owner. No record lands in HubSpot without a resolved owner. Unmatched owner IDs are logged in the pre-migration report.

Rizer's internal record ID is stored on each migrated HubSpot record as a custom property (Source_Rizer_ID__c). This serves two purposes: it enables delta-run de-duplication (if the same Rizer record is re-processed, HubSpot updates rather than duplicates) and it provides traceability back to the source system for audit purposes.

Rizer custom fields are mapped to HubSpot custom properties on the matching object (contact, company, or deal). HubSpot property types are inferred from Rizer's field type metadata: text fields become single-line text or multiple-line text in HubSpot, number fields become number properties, date fields become date properties, and pick-list fields become option-set properties with values mapped individually.

Rizer tags on contacts map to HubSpot contact properties. If tags are free-text labels, we create a HubSpot multi-line text property (Rizer_Tags__c) and populate it with the comma-separated values from Rizer. If tags are structured in Rizer, we evaluate whether to create a corresponding HubSpot option-set property instead.

If Rizer stores loyalty points or a similar numeric score on contacts, we migrate it as a HubSpot number property (Loyalty_Points__c) on the Contact object. This preserves the data for reporting and can be used as a contact property in HubSpot workflows after migration, though the workflow logic itself must be rebuilt in HubSpot.