CRM migration
Field-level mapping, validation, and rollback between Wice CRM and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Wice CRM
Source
monday CRM
Destination
Compatibility
6 of 10
objects map 1:1 between Wice CRM and monday CRM.
Complexity
BStandard
Timeline
3-6 weeks
Overview
Moving from Wice CRM to Monday.com CRM is a schema translation that requires reconstructing Wice's relational CRM objects inside Monday.com's board-and-item model. Wice holds Contacts linked to Organizations, Deals attached to Contacts, Projects with nested Tasks, and a category system for classification; Monday.com represents all of these as board items with column types, labels, and connected boards. Wice publishes no public REST API, so we rely on the built-in CSV export function for cloud installations and direct database queries for on-premise deployments. We export parent records first to preserve relationship IDs, then reconstruct contact-organization links using Monday.com's relation columns and connected boards. Custom pipeline stages require explicit mapping during discovery because Wice allows fully per-installation stage customization. We do not migrate Wice's Reports and Charts as configuration; we deliver the underlying record data and a written recommendation for rebuilding dashboard views in Monday.com.
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 Wice CRM 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.
Wice CRM
Contact
monday CRM
People Item
1:1Wice Contacts map to People items in Monday.com CRM. The Wice contact first name, last name, email, phone, and address fields map to the corresponding Monday.com native column types (Text, Email, Phone, Location). Custom fields on the Wice contact record map to additional columns on the People board. The Wice contact-organization link is preserved separately during migration and reconstructed using Monday.com's relation column once the Organizations have been imported first.
Wice CRM
Organization (Company)
monday CRM
People Item (company column)
1:manyWice Organizations map to Monday.com as People items with the company name stored in the Company column rather than a separate object. This is a structural difference: Wice enforces a separate Organization record that Contacts link to; Monday.com treats company as a property on the People item. We export Organizations first, map the organization name to the company column, and then map Wice Contacts to People items with the company column populated from the matched Organization name. The original Wice Organization-to-Contact relationship ID is preserved in a Text column for audit.
Wice CRM
Deal (Pipeline)
monday CRM
Opportunities Item
1:1Wice Deals map to Opportunities items in Monday.com CRM's Opportunities board. The deal name, value, expected close date, owner, and pipeline stage migrate to the corresponding Monday.com column types. The most critical mapping step is translating Wice's custom pipeline stages to Monday.com Status column values; we capture the customer's actual Wice stage names during discovery and generate a stage-mapping table before any items are written. Stage mapping errors are the primary cause of deal-value misrepresentations post-migration.
Wice CRM
Deal Stage
monday CRM
Status column
lossyWice allows fully per-installation pipeline stage customization. We capture the customer's actual Wice stage names, probabilities, and order during discovery and create a corresponding Status column in Monday.com's Opportunities board with matching label names and probability percentages in a separate Numbers column. Stage order is preserved by setting the Status column's indexing sequence to match Wice's pipeline ordering.
Wice CRM
Project
monday CRM
Board
1:1Wice Projects contain Tasks, assignees, and status fields in a hierarchical structure. Monday.com CRM has no native Project object; we represent each Wice Project as a dedicated Board with Groups representing the project's task sections. We map Wice project custom fields to Board columns, assign Wice project owners as Board members, and use the Status column to represent project-level status. The project-task hierarchy is preserved inside the Board.
Wice CRM
Task
monday CRM
Item (inside Project Board or standalone Board)
1:1Wice Tasks exist inside Projects and also standalone linked to Contacts or Deals. We export both contexts. Tasks inside a Wice Project map to Items within the corresponding Monday.com Board (one Board per Project). Standalone Tasks linked to Deals map to Items in the Opportunities Board tagged with a label identifying the source context. Standalone Tasks linked to Contacts map to Items in the People Board. Orphaned Tasks without a valid parent are flagged for customer review before import.
Wice CRM
Campaign
monday CRM
Board (custom CRM configuration)
lossyWice differentiates basic and advanced campaigns with targeting and tracking properties. Monday.com CRM has no native campaign object; we create a Campaigns Board with columns for campaign name, type, start date, status, and targeting properties sourced from Wice's campaign fields. Campaign tracking data (sent/open/click metrics) does not migrate from Wice as these are generated by connected email tools rather than stored in the CRM. We document which metrics were available in Wice and recommend corresponding reporting in Monday.com.
Wice CRM
Ticket
monday CRM
Cases Item
1:1Wice Tickets linked to Contacts or Organizations map to Items in Monday.com's Work Management Cases board if the destination account includes the Work Management module. Ticket status, priority, and custom fields map to corresponding column types. We note that Wice ticket numbering sequences may reset in Monday.com because Monday.com generates item IDs automatically; the original Wice ticket number is preserved in a Text column for reference.
Wice CRM
Note
monday CRM
Update or File Item
1:1Wice free-text Notes attached to Contacts, Organizations, Deals, and Projects migrate as Updates on the corresponding Monday.com Items with the original timestamp preserved. Rich text formatting (bold, lists) from Wice notes may be simplified to plain text depending on the Update column's rendering. The source-object linkage (note belongs to Contact X, Deal Y) is preserved via a relation column on the Item.
Wice CRM
Custom Properties (Fields)
monday CRM
Custom Columns
lossyWice custom fields on Contacts, Organizations, Deals, and Projects map to Monday.com column types of equivalent data type: Wice text fields map to Text columns, picklist fields to Dropdown or Tags columns, date fields to Date columns, and numeric fields to Numbers columns. Picklist-style custom fields require value translation if the Monday.com dropdown options differ from Wice's option set. We capture all custom field definitions during discovery and pre-create the corresponding columns before data import.
| Wice CRM | monday CRM | Compatibility | |
|---|---|---|---|
| Contact | People Item1:1 | Fully supported | |
| Organization (Company) | People Item (company column)1:many | Fully supported | |
| Deal (Pipeline) | Opportunities Item1:1 | Fully supported | |
| Deal Stage | Status columnlossy | Fully supported | |
| Project | Board1:1 | Fully supported | |
| Task | Item (inside Project Board or standalone Board)1:1 | Fully supported | |
| Campaign | Board (custom CRM configuration)lossy | Fully supported | |
| Ticket | Cases Item1:1 | Fully supported | |
| Note | Update or File Item1:1 | Fully supported | |
| Custom Properties (Fields) | Custom Columnslossy | Mapping required |
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.
Wice CRM gotchas
No publicly documented REST API
Attachment export is a manual step
Custom pipeline stages require explicit mapping
On-premise installations vary by version
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
Export sourcing and discovery
We determine the Wice deployment type (cloud or on-premise) to select the correct data extraction method. For cloud Wice, we guide the customer through the built-in CSV export for Contacts, Organizations, Deals, Projects, Tasks, Tickets, and Notes. For on-premise Wice, we request database access credentials and document the table schema for each object. We capture the actual Wice pipeline stage names, custom field definitions, and category values during discovery. We also inventory the automation equivalents in Wice (any recurring action patterns or workflow-like behaviors) and the attachment volume per object type to scope the manual file-export phase.
Monday.com board schema design
We design the destination Monday.com CRM structure before any data is written. This includes creating the People board (with the company column and relation column for cross-links), the Opportunities board (with Status, Numbers for probability, and Date columns for expected close), a Projects board or separate project boards, and any Campaign and Ticket boards. We configure custom columns to match Wice custom field data types and pre-create picklist values for dropdown columns using Wice's picklist option sets. The board schema is validated in a Monday.com test workspace before production migration begins.
Data export, cleaning, and transformation
We receive the Wice CSV exports or database extracts and run a data quality audit: duplicate detection, incomplete records, inconsistent formatting in address and phone fields. We apply the Wice stage-to-Monday-status mapping table to all Deal records. We split the contact-to-organization relationship by tagging each Contact with its parent Organization name and setting the company column. We transform Wice custom field values to match Monday.com column format requirements. We generate a transformation manifest showing each field's source value, target column, and any transformations applied.
Test migration and reconciliation
We run a full test migration into a Monday.com test workspace using production-like data volume. The customer reconciles record counts across all objects (Contacts in, Organizations in, Deals in, Projects in, Tasks in, Notes in), spot-checks 20-30 random records against the Wice source, and validates that the contact-organization relationship appears correctly in Monday.com. Any mapping corrections and column type adjustments happen in the test workspace. This step typically requires two to three rounds of correction for migrations with complex custom field sets.
Production migration and cutover
We run production migration in dependency order: Organizations first (to populate the company column lookup), then Contacts (with company column set and relation column linked), Deals with stage mapping applied, Projects as boards, Tasks as items within their parent boards, Tickets, and Notes as Updates. Each phase emits a row-count reconciliation report. We freeze Wice writes during the cutover window and run a final delta pass for any records modified during migration. We do not migrate Hold Files attachments; the customer handles the file-export checklist in parallel and uploads files to the corresponding Monday.com Items post-migration.
Validation, automation handoff, and hypercare
We run post-migration validation against the transformation manifest and the Wice source record counts. We deliver the automation inventory document listing every Wice automation equivalent and its recommended Monday.com automation trigger with test instructions. We provide a one-week hypercare window to resolve any record linkage issues, column mapping discrepancies, or automation failures identified by the customer's team. We do not rebuild Wice configurations as Monday.com automations inside the migration scope; any automation rebuild work is a separate engagement handled by the customer's Monday.com admin or a Monday.com partner.
Platform deep dives
Wice CRM
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Wice CRM and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Wice CRM and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Wice CRM and monday CRM.
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
Wice CRM: Not publicly documented.
Data volume sensitivity
Wice CRM 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 Wice CRM to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Wice CRM 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 Wice CRM
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.