CRM migration

Migrate from ConSol to Nutshell

Field-level mapping, validation, and rollback between ConSol and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

ConSol logo

ConSol

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between ConSol and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

ConSol logo

ConSol

What's pushing teams away

  • Limited integration with external CRM systems noted as a frustration in G2 reviews, with users unable to connect ConSol CM to their primary customer platforms.
  • Complex feature set and steep learning curve reported in G2 feedback, with users feeling overwhelmed by information density during onboarding.
  • Perpetual licensing and enterprise pricing structure makes the platform costly for smaller organizations evaluating alternatives.
  • Vendor lock-in concerns with proprietary German-developed platform motivating organizations to evaluate international alternatives with broader ecosystem support.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How ConSol objects map to Nutshell

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

maps to

Nutshell

Lead

1:1
Fully supported

Consol 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

maps to

Nutshell

Person

1:1
Fully supported

Consol 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

maps to

Nutshell

Company

1:1
Fully supported

Consol 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

maps to

Nutshell

Deal

1:1
Fully supported

Consol 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

maps to

Nutshell

Deal

1:1
Fully supported

Consol 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

maps to

Nutshell

Owner / User

1:1
Fully supported

Consol 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

maps to

Nutshell

Note / Custom Field

1:1
Fully supported

Consol 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)

maps to

Nutshell

Task

1:1
Fully supported

Consol 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

maps to

Nutshell

File (via URL reference)

1:1
Fully supported

Consol 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

maps to

Nutshell

Custom Fields on Deal / Lead

1:1
Fully supported

Consol 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.

Gotchas + challenges

What specifically takes care here

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 logo

ConSol gotchas

High

REST API documentation is fragmented across multiple moved URLs

High

Workflow automations and SLA rules are not API-accessible

Medium

Attachment extraction requires a secondary pipeline pass

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Consol CM SLA timers, approval chains, and workflow rules have no Nutshell equivalent

    Consol CM's core value proposition is its BPM engine — SLA response timers, multi-tier approval chains, escalation rules, and conditional routing are all built on Consol CM's workflow designer. Nutshell has no SLA tracking, no multi-step approval routing, and no BPM process engine. When these migrate, the underlying SLA data (response-time elapsed, escalation level, approval status) transfers as custom fields on the Lead or Deal record, but the automated triggers stop. We deliver a Consol CM workflow export so your Nutshell admin can evaluate which rules can be rebuilt using Nutshell's automation tools or a third-party workflow engine.

  • Consol CM incident-to-problem linking does not map to any Nutshell relationship

    Consol CM's data model links incidents to problem records and change requests, forming a known-error-database relationship. Nutshell has no concept of linked incident-problem-change hierarchies. We extract the entire relationship graph and store it as a JSON blob in a custom long-text field on the Lead or Deal record. Post-migration, teams typically import this relationship graph into a separate knowledge-base tool or reconstruct links manually in Nutshell's Deal or Lead records using custom lookup fields.

  • Assignment groups with multiple members collapse to a single Nutshell owner

    Consol CM queues and assignment groups can route work to any member of the group, with the group itself functioning as a shared inbox. Nutshell assigns records to a single user. When a Consol CM assignment group has multiple members, we resolve the record to the group owner by email match, or flag the group for pre-migration user creation in Nutshell. The group ID and member list are preserved as custom fields on the record so your team can manually re-assign or distribute work after migration.

  • Consol CM custom objects and extended attribute fields require Nutshell custom field creation

    Consol CM allows administrators to extend any object with custom attribute fields beyond the standard schema. Nutshell's custom field capability is limited to People, Companies, and Leads. Consol CM custom fields on incident or activity records must be converted to custom fields on Nutshell Leads or Tasks — any custom fields that reference BPM-specific data types (process-state enums, SLA-tier objects, routing rule IDs) store their raw values as text fields in Nutshell. We generate a custom-field creation checklist for the Nutshell side before the migration runs.

  • Nutshell's per-contact email marketing billing has no Consol CM equivalent

    Nutshell charges for email marketing contacts separately from CRM user seats, with pricing tiers based on contact volume. Consol CM has no email marketing module and no contact-based billing. If your team plans to activate Nutshell's built-in email marketing after migration, the contact count for billing purposes starts from zero — there is no carry-over of a Consol CM 'contact' count into Nutshell's marketing contact pool. We flag this distinction during the scoping call so it does not appear as a billing surprise post-migration.

Migration approach

Six steps for a successful ConSol to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

ConSol logo

ConSol

Source

Strengths

  • Combines help desk ticketing with BPM workflow capabilities in a single platform.
  • Intelligent auto-routing assigns requests to appropriate support tiers automatically.
  • ISO 27001 certified cloud deployment meets enterprise security standards.
  • Established in 1984 with a track record of large enterprise deployments in Germany.

Weaknesses

  • Limited public API documentation makes automated data extraction and migration planning difficult.
  • Integration capabilities with external CRMs are constrained, limiting hybrid workflow setups.
  • Steep onboarding curve requires significant training investment before teams become productive.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across ConSol and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    ConSol: Not publicly documented.

  • Data volume sensitivity

    B

    ConSol doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your ConSol to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about ConSol to Nutshell data migrations

Answers to the questions buyers ask most during ConSol to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your ConSol to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Small Consol CM datasets (under 25,000 records with no complex BPM fields) typically complete in 24–72 hours. Larger instances with extensive custom objects, multi-tier assignment groups, and 75,000+ records extend to 7–14 days. The longest phase is mapping Consol CM SLA fields, approval-chain metadata, and BPM process-state variables to Nutshell custom fields — this requires custom field creation on the Nutshell side before data lands. We deliver a detailed timeline estimate after the data audit phase.

Adjacent paths

Related migrations to explore

Ready when you are

Move from ConSol.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day