Migrate from Rizer to monday CRM

Rizer Contacts migrate to Monday.com CRM People Contacts. The core fields (name, email, phone, address) map directly to the Monday.com CRM Contact fields. The Rizer referral source property (e.g., Instagram, TikTok, affiliate link) migrates to a Monday.com CRM text custom field named referral_source__c. Lifecycle stage from Rizer migrates to a dropdown custom field named rizer_lifecycle_stage__c for audit purposes. We deduplicate on email address and flag records with missing email for manual review before insert.

Rizer Company records (linked to Contacts) migrate to Monday.com CRM Companies. Industry tags and company type fields from Rizer map to Monday.com CRM text or dropdown custom fields. Company domain maps to the Website field. If a Rizer Contact has no associated Company, we create a placeholder Company record linked to the Contact for consistency in the Monday.com CRM data model.

Rizer Deals map to Monday.com CRM Deal Items on a pipeline board. The Rizer deal stage (e.g., Appointment Scheduled, Proposal Sent, Won, Lost) maps to a Status column on the Monday.com CRM Deal board. Deal amount, close date, and pipeline name migrate to the corresponding Monday.com CRM columns. If Rizer has multiple pipelines, we create a Monday.com CRM board per pipeline and map accordingly.

Rizer Workflows are property-triggered email sequences with branching logic and delay rules. Monday.com Automations are trigger-action recipes on boards and items. These are architecturally different and we do not migrate Workflows as code. We deliver a written inventory of every active Rizer Workflow documenting its trigger condition, branch logic, delay actions, and CRM field updates, with a recommended Monday.com Automation rebuild approach for the customer's admin.

Rize Clients (the time-tracking product at rize.io) are top-level entities in a separate product with a separate API scope. We treat Rize as a second export pass within this migration. Rize Clients map to Monday.com CRM Companies using the client name, billing email, and any associated project count. The customer's admin decides whether to merge Rize Clients with existing Monday.com CRM Companies or keep them as a separate Company group.

Rize Projects belong to Clients and contain Tasks. We map Rize Projects to Monday.com Work Management boards or to Items on an existing board depending on the customer's structure preference. Project status, description, and start/due dates migrate to corresponding board columns. If the customer wants Deals and Projects in the same workspace, we create a Projects board and link it to the CRM board via Monday.com's cross-board item linking.

Rize Tasks are nested under Projects. Monday.com does not have a native subtask hierarchy within a Project object; instead it uses Subitems attached to Items on a board. We map each Rize Task to a Monday.com Subitem on the parent Project Item. Task status, assignee, and due date migrate to the Subitem fields. Rize subtask booleans (has_subtasks) expand into individual Subitem records.

Rizer and Rize Team Members (user accounts with role assignments) map to Monday.com Workspace Members. We match by email address and resolve the role (admin, manager, member) to a Monday.com team Role assignment. If a Rizer Team Member email has no corresponding Monday.com account, we hold those records in a reconciliation queue for the customer's admin to provision the account before record import resumes.

Rizer Tags are flat string lists applied to Contacts and Workflows. Monday.com uses Labels (color-coded tags on Items) and column-based multi-select options for structured tagging. We offer two strategies during scoping: flat Labels for flexible taxonomy, or a dedicated multi-select custom field if the customer wants structured tag categories (e.g., influencer tier, content type, campaign). The customer selects the strategy before migration.

Rizer stores referral attribution (source channel, campaign name, attribution window) on the Contact record. Monday.com CRM has no native referral tracking object, so we create custom fields on the Contact: referral_source__c (text), referral_campaign__c (text), and referral_date__c (date). The attribution history is preserved as read-only text in the field for reference; the customer rebuilds attribution reporting in Monday.com dashboards manually.