Migrate from Rizer to Freshsales

Rizer Contacts map to Freshsales Lead for records with early lifecycle stages (subscriber, lead) and to Freshsales Contact for records at sales qualified and customer stages. We compute the split using Rizer's lifecycle stage property at transform time and write the original Rizer stage value to a custom field rizer_lifecycle_stage__c on the destination record for audit continuity. Email serves as the dedupe key for both objects. Referral source attribution from Rizer's Contact record maps to a custom field referral_source__c on the destination Lead or Contact.

Rizer Company records map directly to Freshsales Account. The Company domain or website property becomes the Account Website field and the dedupe key during import. Account is created before Contact import so that the AccountId lookup is satisfied at Contact insert. Industry tags and custom company properties migrate to Freshsales custom fields that we pre-create during schema design.

Rize Client records (from the separate rize.io product) map to Freshsales Account objects with a custom field product_source__c = 'Rize' to distinguish them from Rizer Social Company records. We treat the Rize export as a separate scoped pass. Projects and Tasks from Rize map to Freshsales Deals (tagged with a custom pipeline for time-tracking) or to Tasks under the parent Account, depending on the customer's chosen data model in Freshsales.

Rizer Deals map to Freshsales Opportunity. The Rizer dealstage property maps to Freshsales StageName using a stage translation table defined during scoping. Pipeline assignment from Rizer maps to a Freshsales pipeline that we configure before migration. Amount, currency, closing date, and owner all migrate directly. Deals without an associated Company in Rizer receive the AccountId of the nearest parent Company or are held in a reconciliation queue for the customer to resolve before Opportunity import.

Rizer Social Team Members and Rize Team Members both map to Freshsales User records. We resolve by email match against the Freshsales User table. Any Rizer owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role assignments (admin, manager, member) map to Freshsales role hierarchy entries that we document during scoping.

Rizer's Referrizer custom fields are key-value pairs stored as strings without enforced type constraints. We inspect raw values during the extract phase and infer data type (date, number, multi-select, text) before writing to Freshsales custom fields of matching type. Multi-select fields stored as comma-delimited text in Rizer are split and written to Freshsales multi-select picklist fields. We pre-create all Freshsales custom fields in the destination account before any record migration begins so that import rows are not rejected for unknown column headers.

Rizer Workflow sequences attached to Contact lifecycle stage transitions and tag triggers do not migrate to Freshsales because the trigger model and action set differ. We extract every active Workflow with its trigger conditions, delay rules, branching logic, and CRM actions and deliver them as a written inventory document. The customer's admin rebuilds each workflow in Freshsales' Automation section (available from Growth plan) using the inventory as a configuration guide.

Rizer tags applied to Contacts are flat string lists. We map these to Freshsales multi-select picklist fields on the Lead or Contact object. We scope the tag vocabulary during discovery and pre-create the picklist values in Freshsales so that import rows with tag values are not rejected. Tags used for referral segmentation map to the referral_source__c custom field instead.