Migrate from Rizer to Zoho CRM

Rizer Contacts map to Zoho CRM Leads by default. If the customer's Rizer Contacts include a lifecycle stage indicating they are active customers rather than prospects, we map them to Zoho CRM Contacts attached to an Account. We inspect the lifecycle stage field (if present) to determine the split. Standard contact fields (name, email, phone, address) map directly; referral attribution data stored on the Contact becomes a custom field in Zoho CRM.

Rizer Company records map directly to Zoho CRM Accounts. The company name becomes the Account Name, industry tags map to the Industry picklist, and any custom company properties become Zoho CRM custom fields. We use the Account Name as the dedupe key during import to prevent duplicate Account creation. If no Rizer Company is linked, the Contact import creates an Account using the Contact's company name as a fallback.

Rizer Deals map to Zoho CRM Deals. The deal amount, stage, and close date map to Amount, Stage, and Closing Date. We map the Rizer deal pipeline to a Zoho CRM pipeline by creating the equivalent pipeline in Zoho before migration. Deals without a linked Contact resolve to an Account-level Deal; Deals with a linked Contact receive the Contact's Account as the parent Account in Zoho.

Rize Clients (from the time-tracking product) map to Zoho CRM Accounts as a separate pass in the migration. We use CSV export from Rize to extract Client records and import them into Zoho CRM Accounts with a custom field source_system__c set to 'Rize' to distinguish them from Accounts migrated from Rizer Social. If the customer uses both products, we deduplicate by company name before writing.

Rize Projects map to Zoho CRM Deals tagged with a Project record type. Each Project's associated Tasks migrate as Zoho CRM Tasks linked to the parent Deal via the WhatId field. This preserves the project-task hierarchy while fitting Zoho's CRM-centric module structure. Projects without a linked Client resolve to an Account-less Deal for the customer admin to reassign post-migration.

Rize Tasks map to Zoho CRM Tasks. The task subject, description, due date, and status transfer directly. If the Rize Task has a subtask flag (stored as a boolean or count in Rize), we expand it into discrete Zoho CRM Task records with a parent reference. Assigned user resolves by email match against Zoho CRM Users.

Rize Team Members map to Zoho CRM Users. Role assignments (admin, manager, member) from Rize map to Zoho CRM Profile or Role assignments. We match by email address. Team Members without a matching Zoho CRM User go to a reconciliation queue for the customer's admin to provision. We do not migrate inactive users unless explicitly requested.

Rizer's Referrizer API returns custom field key-value pairs without enforcing type constraints. Date fields stored as strings, multi-select fields stored as delimited text, and numeric fields stored as text all appear identically in the API response. We infer the data type by inspecting raw values before writing to Zoho CRM, and we create typed custom fields in Zoho CRM matching the inferred type. This prevents silent type coercion errors in Zoho's validation rules.

Rizer tags applied to Contacts and Deals migrate to Zoho CRM multi-select picklist fields on the equivalent module. We inspect the tag vocabulary during discovery and create the picklist values in Zoho CRM before import. If the customer uses more than 150 distinct tags, we default to a text field to avoid picklist value limits and document the tag taxonomy for manual cleanup.

Rizer's referral attribution (source, medium, campaign, attribution window) is stored as fields on the Contact record. We map these to Zoho CRM custom fields on the Contact or Lead module: referral_source__c, referral_medium__c, referral_campaign__c, and attribution_window__c. The values transfer as text or date depending on the field type. Attribution history spanning multiple fields concatenates into a single reference field.

Rizer Workflow sequences attached to Contact lifecycle stages do not migrate to Zoho CRM as automation code. The trigger conditions (lifecycle stage transitions, tag additions, callback dates), delay rules, and email actions are documented in a written Workflow inventory we deliver to the customer. Zoho CRM Blueprint rules require rebuilding in Zoho's visual builder. We flag which Contacts have active Workflow associations so they are not orphaned during migration.

Rizer email engagement history on Contact records migrates to Zoho CRM Notes or Tasks depending on the customer's preference. Email body and timestamp transfer as a Note with the timestamp preserved in the Note title or description. We batch these as bulk inserts to stay within Zoho's API credit budget. Email attachments migrate as file uploads linked to the parent Contact or Account via ContentDocumentLink.