Migrate from Rizer to Nutshell

Rizer Contacts map to Nutshell People. Standard fields (name, email, phone, address) map directly. The Rizer contact ID is preserved in a custom field rizer_contact_id__c for reconciliation. Tags on Rizer Contacts map to Nutshell label associations on People. Custom fields on Contacts (including referral attribution fields) are migrated to Nutshell custom fields on Person.

Rizer Companies map to Nutshell Companies. The Rizer company association on a Contact is preserved via the Nutshell Company lookup on Person. Industry tags and custom company properties from Rizer map to Nutshell Company custom fields. The Rizer company ID is preserved in rizer_company_id__c for reconciliation.

Rize Clients are a separate product from Rizer Social but represent billable entities that map to Nutshell Companies. We run a second scoped export from Rize (rizersocial.io vs rize.io login) and merge Client records into the Nutshell Companies object, using the Client name as the Company name and the Client ID preserved in rizer_client_id__c. If a Company with the same name already exists from the Rizer Social export, we match on name and link rather than create a duplicate.

Rize Projects belong to Clients and contain Tasks. We map Projects to Nutshell Deals, tagging each Deal with the parent Company (from the Rize Client mapping). The Project name becomes the Deal name, and project status maps to Deal stage using a configured stage set in Nutshell. Projects that have no associated Client are attached to a placeholder Company record created during migration.

Rize Tasks nested under Projects are represented as Nutshell Tasks linked to the parent Deal. Nutshell does not have a native subtask object, so we create a flat task list with the project hierarchy preserved as a prefix in the task name (e.g., ProjectName - TaskName) and the parent Deal reference on each task. Billable hours from Rize are stored in a custom field on the Nutshell Task.

Rizer stores referral attribution sources and attribution windows on Contact records. We map the referral_source field to a Nutshell custom field on Person called referral_source__c, and the attribution_window field to referral_window__c. Attribution history spanning multiple fields is flattened into a single custom text field with pipe-delimited values for audit purposes.

Rizer Workflows are email automation sequences triggered by contact lifecycle stage transitions. These do not migrate to Nutshell because Nutshell's automation model (Autoplay and CRM workflows) uses different trigger conditions and action types. We extract every active Rizer Workflow definition (trigger, conditions, delay rules, tag actions) and deliver a written inventory with a Nutshell Autoplay rebuild recommendation for each.

Rizer Tags are flat string lists applied to Contacts. These map to Nutshell Labels on People. We preserve the tag string exactly and create a corresponding Label in Nutshell during the import phase. Multi-select tag scenarios (contacts with multiple tags) create multiple Label associations per Person.

Rizer and Rize Team Members map to Nutshell Users. We resolve by email match against the Nutshell destination account's existing user list. Any Rizer owner referenced on a Contact or Deal without a matching Nutshell User is placed in a reconciliation queue for the customer to provision before record import resumes.