CRM migration
Field-level mapping, validation, and rollback between ConSol and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
ConSol
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between ConSol and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Consol CM stores data across incidents, service requests, changes, problems, knowledge-base articles, and BPM process instances. Its data model treats tickets as case records with SLA timers, priority levels, assignment groups, and multi-tier categorization. Nutshell operates a simpler schema centered on People, Companies, Leads, Deals, and Tasks — with optional custom fields on People, Companies, and Leads. There is no native incident, change, problem, or SLA-tracking object in Nutshell. We extract all Consol CM records via the platform API, map them to Nutshell objects, and load them through Nutshell's import API with field-level validation. SLA metadata, assignment-group hierarchies, change IDs, and BPM process-state fields have no Nutshell equivalent — those get preserved as custom text fields or surfaced in a pre-migration rebuild reference so your Nutshell admin can reconstruct the logic manually. Consol CM workflows, approval chains, and SLA rules do not migrate; they require a complete rebuild in Nutshell's automation tools or a separate workflow engine. Activities logged against Consol incidents (calls, emails, notes) transfer as Nutshell Tasks, maintaining original timestamps and owner assignments. A 24–48-hour delta-pickup window covers in-flight records during cutover, and a field-level sample diff runs before the full migration commits.
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 ConSol object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
ConSol
Incident / Service Request
Nutshell
Lead
1:1Consol CM incidents and service requests have no direct Nutshell equivalent. Open incidents map to Nutshell Leads so they appear in the sales pipeline; closed incidents map as historical Lead records with status='Closed - Migrated'. SLA metadata, assignment groups, and priority levels are preserved as custom fields on the Lead.
ConSol
Person / Contact
Nutshell
Person
1:1Consol CM person records map 1:1 to Nutshell People. Name, email, phone, address, title, and owner assignment carry over directly. Multi-address records collapse to a single primary address; secondary addresses are appended to a custom text field. The original Consol CM person ID is preserved in a source_id custom field for traceability and delta-run de-duplication.
ConSol
Company / Account
Nutshell
Company
1:1Consol CM company records map to Nutshell Companies. Name, website, industry, employee count, and annual revenue transfer directly. Parent-company hierarchies in Consol CM map using Nutshell's parent-company field when available; deep hierarchies surface as a custom field for manual reorganization.
ConSol
Change Request
Nutshell
Deal
1:1Consol CM change requests are treated as pipeline opportunities in Nutshell. The change ID, risk level, and approval status are preserved as custom fields. Approved and implemented changes land as Won Deals; rejected changes become Lost Deals with the rejection reason stored in a custom field.
ConSol
Problem Record
Nutshell
Deal
1:1Consol CM problem records have no Nutshell equivalent and must transfer as custom fields on a linked Deal or Lead record. The problem ID, root-cause description, known-error-flag, and any associated incident linkage data are preserved as text fields in Nutshell. This preserves traceability so your Nutshell admin can manually reconnect problem relationships using Nutshell's native linking capabilities post-migration.
ConSol
Assignment Group
Nutshell
Owner / User
1:1Consol CM assignment groups (queues) map to Nutshell users by email match. When an assignment group contains multiple members, records distribute to the group owner or the user specified in the Consol CM routing rule. Unmatched groups are flagged before migration so your team can pre-create Nutshell users.
ConSol
Knowledge Base Article
Nutshell
Note / Custom Field
1:1Consol CM knowledge-base articles have no Nutshell equivalent. Articles are exported as a structured CSV with full metadata (title, body, author, created date, tags) and can be imported into Nutshell's built-in document storage or linked to a dedicated knowledge-base tool. Article IDs are preserved in the CSV for traceability back to the original Consol CM system.
ConSol
Activity (Call / Email / Note)
Nutshell
Task
1:1Consol CM activity logs (calls, emails, notes) map to Nutshell Tasks. Task type, subject, body, start time, duration, and owner transfer directly. Parent-record links to Consol incidents are preserved as custom fields on the Task so the relationship is visible in Nutshell.
ConSol
Attachment / File
Nutshell
File (via URL reference)
1:1Consol CM file attachments are exported to a secure cloud-storage bucket (S3-compatible) and linked via a URL custom field on the target Nutshell record. File metadata including original filename, upload date, file size, and MIME type is serialized in the same custom field to preserve full context after migration.
ConSol
BPM Process Instance
Nutshell
Custom Fields on Deal / Lead
1:1Consol CM BPM process-instance state — including step position, process variables, stage timestamps, and active workflow chain — has no Nutshell equivalent. The full process-instance state is extracted as a JSON blob and stored in a long-text custom field on the associated Deal or Lead record. This provides a complete reference for your Nutshell admin to manually reconstruct workflows using Nutshell's automation tools or a separate workflow engine.
| ConSol | Nutshell | Compatibility | |
|---|---|---|---|
| Incident / Service Request | Lead1:1 | Fully supported | |
| Person / Contact | Person1:1 | Fully supported | |
| Company / Account | Company1:1 | Fully supported | |
| Change Request | Deal1:1 | Fully supported | |
| Problem Record | Deal1:1 | Fully supported | |
| Assignment Group | Owner / User1:1 | Fully supported | |
| Knowledge Base Article | Note / Custom Field1:1 | Fully supported | |
| Activity (Call / Email / Note) | Task1:1 | Fully supported | |
| Attachment / File | File (via URL reference)1:1 | Fully supported | |
| BPM Process Instance | Custom Fields on Deal / Lead1:1 | 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.
ConSol gotchas
REST API documentation is fragmented across multiple moved URLs
Workflow automations and SLA rules are not API-accessible
Attachment extraction requires a secondary pipeline pass
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Audit Consol CM data model and extract record taxonomy
We connect to the Consol CM instance using API credentials with read-only access and enumerate all standard and custom objects, field names, and relationship schemas. This gives us the complete field inventory for mapping, flags Consol-specific BPM fields that have no Nutshell equivalent, and identifies assignment groups that need pre-migration user creation in Nutshell. We deliver a data-dictionary report and a custom-field creation checklist for the Nutshell side before any data moves.
Build field-level mapping and create Nutshell custom fields
We build the mapping matrix that translates each Consol CM field to its Nutshell counterpart, including value-mapping tables for pick-list fields (priority, status, industry, person type) and transformation rules for owner resolution by email. For Consol CM BPM fields, SLA metadata, and assignment-group IDs, we create the corresponding custom fields in Nutshell. The mapping matrix is reviewed and approved by your team before the sample migration runs.
Create Nutshell users and resolve ownership
We match Consol CM owners and assignment-group members to Nutshell users by email address. Any Consol CM owner with no matching Nutshell user is flagged with a recommendation to create the user account before migration. Assignment-group hierarchies are flattened: each group member receives records assigned to them individually post-migration, with the original group ID preserved in a custom field for traceability.
Run sample migration with field-level diff
A representative slice of 100–500 records — spanning People, Companies, Leads, and Activities — migrates to Nutshell first. We generate a field-level diff comparing each source field value against its destination value, so you can verify priority and SLA tier mappings, status transformations, owner resolution, and custom field population before the full run commits. Mapping adjustments are made and validated in a second sample pass if needed.
Execute full migration with delta-pickup window
The full Consol CM dataset loads into Nutshell in sequence — People and Companies first, then Leads (including migrated incidents) linked to their resolved owners, then Activities linked to their parent records. A 24–48-hour delta-pickup window captures any Consol CM records created or modified during the cutover period. All operations are logged in an audit trail, and one-click rollback reverts the Nutshell instance to its pre-migration state if reconciliation fails.
Platform deep dives
ConSol
Source
Strengths
Weaknesses
Nutshell
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 ConSol and Nutshell.
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
ConSol: Not publicly documented.
Data volume sensitivity
ConSol 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 ConSol to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your ConSol to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave ConSol
Other ways to arrive at Nutshell
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.