CRM migration
Field-level mapping, validation, and rollback between Referrizer and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Referrizer
Source
monday CRM
Destination
Compatibility
7 of 11
objects map 1:1 between Referrizer and monday CRM.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Referrizer to Monday.com CRM is a structural migration that combines a platform shift (from referral-first marketing CRM to visual work-management CRM) with a data model translation. Referrizer stores Contacts with embedded loyalty points, review request history, and campaign engagement as contact properties; Monday.com separates People (contacts), Deals (opportunities), and Organizations (companies) into distinct board item types with custom columns. We extract Contacts via Referrizer's paginated API (100 records per page), separate loyalty point balances and review request logs from standard contact properties during transformation, and load them as typed custom columns in Monday.com. Multi-location scoping is preserved as location-based tags. Smart Inbox message history is not accessible via the Referrizer API and is explicitly excluded from migration scope. Referrizer automations (campaign triggers, loyalty rules, review request sequences) do not migrate to Monday.com's automation builder; we deliver a written inventory for your admin to rebuild.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Referrizer object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Referrizer
Contact
monday CRM
People (Contact item)
1:1Referrizer Contacts map to Monday.com People items. Standard fields (name, phone, email, address) migrate directly to equivalent People columns. Custom fields are enumerated via GET /contacts before migration, then recreated as typed custom columns (text, number, date, dropdown) in Monday.com. Multi-location contacts are tagged with location labels during transformation to preserve location scoping. Labels from Referrizer migrate as tag column values on the People item.
Referrizer
Company
monday CRM
Organization
1:1Referrizer Company records map to Monday.com Organizations. The company name, domain, phone, and address fields translate to the corresponding Organization fields. Organizations are created before People items so that the organization-person link is established at load time. If Referrizer contacts reference companies without explicit Company records, we create Organization records on-the-fly from the contact's company name field.
Referrizer
Pipeline / Deal Stage
monday CRM
Deal (Opportunity item) + Board columns
1:1Referrizer Pipeline stages map to Monday.com Deal items on a Deals board, with the stage name becoming a Status column value. The Deal item receives the contact's People item as the primary person link and the organization's Organization item as the linked organization. Deal value, expected close date, and stage probability migrate as custom columns. Stage ordering is preserved per the Referrizer pipeline configuration.
Referrizer
Loyalty Points
monday CRM
Custom Number Column (People item)
lossyReferrizer stores loyalty point balances as numeric custom properties on Contact records rather than a distinct object. We identify loyalty-related fields during schema enumeration, separate them from standard contact properties, and recreate them as custom number columns on the People item in Monday.com. The customer decides the column name during scoping. Monday.com has no native loyalty object; the points value is maintained as a plain number field accessible on the contact record.
Referrizer
Campaign
monday CRM
Board or Item Group + Tags
1:1Referrizer Campaigns (Regular and Automated) are exported with their type, status, start date, and associated contacts. Each campaign maps to a tagged group of People items or a dedicated Board in Monday.com, depending on the customer's intended use case. Campaign engagement metrics (sent, delivered, opened counts from Referrizer's Reports API) are stored as number columns on the campaign group. The customer chooses whether to use a single board with groups or separate boards per campaign type during scoping.
Referrizer
Offer / Referral Code
monday CRM
Custom Text Column (People or Deal item)
lossyReferrizer Offers track promotional codes and referral relationships between contacts. Offer codes and reward structures are stored as text columns on the associated People or Deal item, depending on whether the referral is contact-centric or deal-centric in the customer's workflow. We export offer name, code, reward type, and reward value as separate columns and remap them to Monday.com text or number fields accordingly.
Referrizer
Review Request
monday CRM
Custom Column + Activity Log (People item)
lossyReferrizer review request history (which contacts received requests, when, and to which platform: Google, Yelp, or Facebook) is stored as activity on the Contact object. We export review request events as date columns and platform labels on the People item in Monday.com, with the status of the request (pending, requested, reviewed) captured as a dropdown column. Review links and ratings are stored as text fields if present in the source data.
Referrizer
Label / Segment
monday CRM
Tag Column (People item)
1:1Referrizer contact labels and segments export as tag arrays on each Contact record. These map directly to Monday.com's Tag column on the People item. Multi-label contacts receive all applicable tags. Tags are preserved as-is with no rename or merge unless the customer requests consolidation during scoping. If the customer used label hierarchies, we flatten them to a single tag string per level.
Referrizer
Activity / Engagement Feed
monday CRM
Activity Log Column (People item)
1:1Referrizer activity feed events (UTM tracking data, campaign opens, link clicks) are accessible via contact activity endpoints. We export activity events as timeline entries in a text column or connected subitem on the People item, with event type, timestamp, and source preserved. Note that Smart Inbox message content is not accessible via API and is excluded from this mapping; only campaign-level engagement metrics from the Reports API can be migrated.
Referrizer
User / Team Member
monday CRM
Team Member (Workspace user)
1:1Referrizer team members and role assignments export with name and email. These map to Monday.com Workspace members by email match. Role-based permission structures (admin, manager, member) are documented but do not have a direct Monday.com equivalent in the CRM tier; permissions in Monday.com are board-level and workspace-level assignments rather than platform-wide role definitions. We preserve the role designation in a custom dropdown column on the People item for reference.
Referrizer
Location (Multi-location)
monday CRM
Location Tag (People item)
lossyReferrizer's multi-location model associates contacts with specific business locations. We query and scope exports by location account ID to prevent cross-contamination, then apply a location tag to each migrated People item in Monday.com. The tag value uses the location name from Referrizer. If the customer needs location-level reporting in Monday.com, we recommend creating a separate Board per location with an inherited location tag column rather than a single board with location filters.
| Referrizer | monday CRM | Compatibility | |
|---|---|---|---|
| Contact | People (Contact item)1:1 | Fully supported | |
| Company | Organization1:1 | Fully supported | |
| Pipeline / Deal Stage | Deal (Opportunity item) + Board columns1:1 | Fully supported | |
| Loyalty Points | Custom Number Column (People item)lossy | Fully supported | |
| Campaign | Board or Item Group + Tags1:1 | Fully supported | |
| Offer / Referral Code | Custom Text Column (People or Deal item)lossy | Fully supported | |
| Review Request | Custom Column + Activity Log (People item)lossy | Fully supported | |
| Label / Segment | Tag Column (People item)1:1 | Fully supported | |
| Activity / Engagement Feed | Activity Log Column (People item)1:1 | Fully supported | |
| User / Team Member | Team Member (Workspace user)1:1 | Fully supported | |
| Location (Multi-location) | Location Tag (People item)lossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Referrizer gotchas
No bulk export API — migration relies on Zapier or CSV
Smart Inbox conversations are not accessible via API
Loyalty points stored as contact properties, not a distinct object
Rate limits not publicly documented
Multi-location scoping required to avoid cross-contamination
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Schema enumeration and scoping
We extract the full Referrizer contact schema via paginated GET /contacts requests to enumerate all custom field names, types, and values. We identify loyalty-related numeric fields, review request history fields, and label definitions. For multi-location accounts, we query location IDs and confirm the location scope with the customer before extraction. We produce a schema inventory document listing every field to be migrated, its type, and its destination column in Monday.com.
Contact and company extraction in dependency order
We extract Referrizer contacts in page-by-page batches (100 records per page) with exponential backoff on 429 responses. Referrizer company records are extracted separately and in parallel. Contacts referencing companies are held until company records are loaded into Monday.com as Organizations so that the organization link is established at insert time. All extraction outputs are validated against API record counts before transformation begins.
Transformation and field mapping
We transform the extracted data into Monday.com CSV import format. Custom fields are recreated as typed columns (text, number, date, dropdown, tag) in Monday.com before import. Loyalty point fields are isolated and mapped to custom number columns. Review request history is mapped to date and dropdown columns on the People item. Labels are mapped to tag column values. Location scoping is applied as location tags on each contact record. The transformation output is a validated CSV ready for Monday.com import.
Monday.com workspace setup and board configuration
We create the Monday.com workspace with People (Contacts), Deals (Opportunities), and Organizations boards. Custom columns are provisioned to match the transformed schema. Pipeline stages are configured as Status column values on the Deals board. If the customer requests separate boards per campaign or per location, these are created at this step. The workspace is configured in a sandbox or staging environment first for validation before production migration.
Production migration and reconciliation
We run the production migration into the configured Monday.com workspace. Organizations are loaded first, then People items with organization links established, then Deals with person and organization links. Each phase emits a row-count reconciliation report against the source extraction totals. Deduplication checks run against email address as the primary key. Any records that fail import (format errors, missing required fields) are routed to a correction queue for customer review before retry.
Cutover, validation, and automation handoff
We freeze Referrizer writes during cutover and run a final delta migration of any records modified during the migration window. Monday.com becomes the system of record once validation is complete. We deliver the automation inventory document listing every Referrizer campaign automation requiring rebuild in Monday.com's automation builder. We support a 5-business-day hypercare window for reconciliation issues. Workflow rebuild, team training, and post-migration admin support are outside standard migration scope and can be scoped as a separate engagement.
Platform deep dives
Referrizer
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Referrizer and monday CRM.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Referrizer: Not publicly documented; API returns 429 TOO_MANY_REQUESTS on overages.
Data volume sensitivity
Referrizer doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Referrizer to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Referrizer to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Referrizer
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.