CRM migration

Migrate from Black Ice CRM to Nutshell

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

Black Ice CRM logo

Black Ice CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

67%

6 of 9

objects map 1:1 between Black Ice CRM and Nutshell.

Complexity

BStandard

Timeline

1-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Black Ice CRM to Nutshell is a migration from a niche UK platform with uncharted API access and per-feature billing to a US-established CRM with per-user pricing, a documented REST API, and an active integration ecosystem. Black Ice CRM holds a full sales cycle (Leads through Invoices) in a schema that varies by deployment, while Nutshell organises data around People, Companies, Deals, and Tasks with optional Quotes, Products, and Activities. We extract via Black Ice's built-in export utility or database backup, audit the actual field set before mapping, and load into Nutshell in dependency order: People and Companies first, then Deals, then Quotes with their line items, then Orders and Invoices as configuration records, and finally Products with stock levels. Automations, picking list documents, and custom field structures do not migrate as code; we deliver a written inventory of each for the customer's admin to rebuild in Nutshell.

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

Black Ice CRM logo

Black Ice CRM

What's pushing teams away

  • Minimal online presence and thin documentation make it difficult for teams to evaluate fit, get support answers, or find third-party integrations independently.
  • The platform appears to serve a narrow UK market with limited community resources, leaving users without the peer-driven knowledge bases available for larger CRM platforms.
  • Per-feature pricing can become costly as teams add modules, and the lack of transparent tier descriptions makes it hard to predict total cost of ownership at scale.
  • Limited known API surface and third-party integration ecosystem means teams requiring deep third-party connections may find the platform constraining.
  • Small user base means fewer pre-built migration guides, template configurations, and third-party consultants available compared to mainstream CRMs.

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 Black Ice CRM objects map to Nutshell

Each row shows how a Black Ice CRM 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.

Black Ice CRM

Account

maps to

Nutshell

Company

1:1
Fully supported

Black Ice Accounts map to Nutshell Companies. Company name, address fields, and phone map directly. We require a pre-migration export sample to identify any custom fields on the Account module that need to be created as Nutshell custom fields before import. Account is imported before any People records so the Company lookup is satisfied at insertion time.

Black Ice CRM

Contact

maps to

Nutshell

Person

1:1
Fully supported

Black Ice Contacts map to Nutshell People. Email, phone, name, title, and address fields migrate directly. The contact-to-account relationship maps to the People-Company association in Nutshell, which we resolve after both Company and People imports are complete. Any custom contact fields identified in the pre-migration audit create Nutshell custom fields on the Person object before data loads.

Black Ice CRM

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Black Ice Leads map to Nutshell Leads. We use a pre-migration field audit to capture the actual lead fields active in the deployment, as Black Ice lead fields vary by installation. Lead status, source, and owner assignment map to Nutshell's lead_status, lead_source, and assignee fields. Leads that have already been converted to Contacts in Black Ice are handled as Contacts in Nutshell to avoid duplication.

Black Ice CRM

Potential Tracking / Pipeline

maps to

Nutshell

Deal

1:1
Fully supported

Black Ice Potential Tracking records map to Nutshell Deals. The pipeline stage name from Black Ice maps to the Deal's status field in Nutshell, and estimated value maps to deal_value. We capture any custom stage names used in Black Ice and map them to existing or new Nutshell Deal statuses during the scoping call.

Black Ice CRM

Quote

maps to

Nutshell

Quote

1:1
Fully supported

Black Ice Quotes map to Nutshell Quotes where the customer holds an active Quotes module. Quote header fields (quote number, date, total) map directly, and line items migrate as Quote Line Items linked to the Quote. If the customer does not hold the Quotes module in Black Ice, this object is omitted. Quote PDF attachments migrate as file links against the Quote record.

Black Ice CRM

Order

maps to

Nutshell

Deal (configuration record)

lossy
Fully supported

Black Ice Orders do not have a direct Nutshell equivalent because Nutshell is a CRM rather than an ERP. We map Orders as Nutshell Deals with a custom field order_number__c and a Deal status that reflects the order's fulfillment state (e.g., Awaiting Fulfillment, Shipped, Delivered). Line items from the Black Ice Order migrate as Deal Products attached to the Deal. This is a semantic configuration, not a field-for-field map, and we document the mapping logic in the migration spec.

Black Ice CRM

Invoice

maps to

Nutshell

Deal (configuration record)

lossy
Fully supported

Black Ice Invoices similarly do not have a native Nutshell equivalent. We map Invoices as Nutshell Deals with a custom field invoice_number__c, a Deal status reflecting payment state (e.g., Invoiced, Partially Paid, Paid), and a monetary amount field carrying the invoice total. Payment status from Black Ice migrates as a custom field on the Deal. This approach preserves the financial record context in the CRM without requiring an accounting integration.

Black Ice CRM

Product

maps to

Nutshell

Product

1:1
Fully supported

Black Ice Product records (name, SKU, price) map to Nutshell Products. Product descriptions and any custom fields on the Black Ice Products module migrate as Nutshell Product custom fields. We note that Nutshell Products do not include automated stock tracking; current stock quantities from Black Ice migrate as a custom field stock_quantity__c on the Nutshell Product, and the customer configures any reorder logic manually in Nutshell post-migration.

Black Ice CRM

Stock / Inventory

maps to

Nutshell

Product (custom field)

lossy
Mapping required

Black Ice stock levels and reorder thresholds do not have a native Nutshell equivalent. We carry forward the current stock quantity as a custom field on the Nutshell Product record and the reorder threshold as stock_reorder_threshold__c. These are static values at the time of migration; live inventory updates are not supported in Nutshell CRM and require a third-party inventory management tool or a custom integration post-migration. We flag this distinction during scoping so the customer plans accordingly.

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.

Black Ice CRM logo

Black Ice CRM gotchas

High

Per-feature pricing obscures true migration scope

High

No publicly documented API schema or rate limits

Medium

Fully customisable modules create unpredictable schema

Medium

Picking list and stock alert data may not export cleanly

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

  • Black Ice CRM has no publicly documented API

    We found no public API schema, developer portal, OpenAPI specification, or rate-limit documentation for Black Ice CRM across the research corpus. Migration cannot proceed via API authentication. We must use Black Ice's built-in application export utility or a database-level export if accessible, and we confirm export method availability during the discovery call. If the export utility is unavailable or produces incomplete data, we escalate before committing to a migration timeline.

  • Per-feature pricing requires active-module audit before scope finalisation

    Black Ice CRM charges $28 per feature per month. We must identify which modules the customer has active (Leads, Accounts, Quotes, Orders, Invoices, Products, Stock Management) during scoping, because each active feature represents a separate data volume and cost context. Activating a previously unused module post-migration can trigger unexpected billing. We confirm active modules with the customer before finalising the migration scope and do not assume all modules are in use.

  • Automations, workflows, and sequences do not migrate

    Nutshell's page-based marketing automations, drip sequences, and deal automation rules are structured differently from any automation capabilities Black Ice CRM may hold. We do not migrate automations as code. We deliver a written inventory of every active Black Ice automation with its trigger, conditions, and actions, along with a recommendation for the equivalent Nutshell automation to use. The customer's admin rebuilds these in Nutshell post-migration. We do not provide post-migration admin support for automation rebuild as standard scope.

  • Black Ice fully customisable module schema requires pre-migration field audit

    Black Ice CRM modules are described as fully customisable, meaning the standard field set varies between deployments. A customer's Accounts module may include custom fields not present in another Black Ice installation. We require a pre-migration field audit — via a sample export or a screen walkthrough — to document the actual schema before building the mapping spreadsheet. Without this step, we cannot guarantee field completeness in Nutshell.

  • Quote-Order-Invoice chain maps to Deals in Nutshell, not native objects

    Black Ice CRM holds Quotes, Orders, and Invoices as separate native objects with parent-child relationships. Nutshell does not have native Order and Invoice objects; Quotes are optional. We map Orders and Invoices as Nutshell Deals with custom fields (order_number__c, invoice_number__c, payment_status__c). The Quote-Order-Invoice relationship chain is preserved by linking each Deal record to its originating and derived counterparts, but this is a semantic configuration that the customer must validate against their financial reporting requirements.

Migration approach

Six steps for a successful Black Ice CRM to Nutshell data migration

  1. Discovery and export method confirmation

    We confirm which Black Ice CRM modules are active, identify the available export method (application export utility or database backup), and obtain a sample export covering Accounts, Contacts, Leads, and any active sales-cycle modules. We pair this with a Nutshell account review to confirm the destination edition and available objects (People, Companies, Deals, Quotes, Products). The discovery output is a written migration scope confirming active modules, estimated record counts per object, and the confirmed export method. We do not proceed to mapping without a sample export.

  2. Pre-migration field audit and schema design

    We review the Black Ice sample export to document the actual field set across all active modules, identifying standard fields, custom fields, and any non-standard field names. We then design the Nutshell schema: creating any required custom fields on People, Companies, Leads, Deals, Quotes, and Products; defining Deal statuses to match Black Ice pipeline stages; and configuring the custom fields used for Order and Invoice semantics (order_number__c, invoice_number__c, payment_status__c, stock_quantity__c). The customer reviews and approves the schema design before any data moves.

  3. Sandbox migration and reconciliation

    We run a test migration into a Nutshell sandbox using the production-equivalent data volume from the sample export. The customer's admin reconciles record counts, spot-checks 25-50 records for field-level accuracy, and verifies that the Order-Invoice semantic mapping meets financial record requirements. Any mapping corrections or missing fields are addressed in the sandbox before production migration begins. This step prevents correction cycles in the production environment where data has already been committed.

  4. Owner reconciliation and User provisioning

    We extract every distinct Black Ice CRM user referenced on Accounts, Contacts, Leads, Deals, and sales-cycle records and match by email against the Nutshell destination account's User list. Any Black Ice owner without a matching Nutshell User goes to a reconciliation queue. The customer's Nutshell admin provisions missing Users before record import resumes. Owner assignment on Deals, Leads, and People cannot be resolved without an active Nutshell User record.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Companies first (as the lookup anchor), then People with Company association resolved, then Leads, then Deals with stage and owner resolved, then Products, then Quotes with line items, then Order-semantic Deals (with order_number__c set), then Invoice-semantic Deals (with invoice_number__c and payment_status__c set), and finally custom field values on existing records. Each phase emits a row-count reconciliation report before the next phase begins. We use Nutshell's native import tools for bulk loads and the Nutshell Power API for large-volume record sets with rate-limit handling.

  6. Cutover, validation, and automation inventory delivery

    We freeze Black Ice CRM writes during cutover, run a final delta migration of any records created or modified during the migration window, then enable Nutshell as the system of record. We deliver the automation inventory document listing every active Black Ice automation with trigger, conditions, actions, and recommended Nutshell equivalent, and the Picking List and Inventory Context note clarifying which stock data carried forward and what requires manual post-migration configuration. We support a five-business-day hypercare window for reconciliation issues. We do not rebuild automations or configure Nutshell's native tools as standard migration scope; these are separate engagements.

Platform deep dives

Context on both ends of the pair

Black Ice CRM logo

Black Ice CRM

Source

Strengths

  • Full sales-cycle coverage from Leads through Quotes, Orders, Invoices, and Products/Stock in a single platform.
  • Built-in inventory and product management with automatic stock reduction on order creation.
  • Per-feature pricing at $28/feature/month lets small teams start lean without paying for unused modules.
  • Fully customisable modules let teams adapt the CRM to existing workflows rather than reshape processes.
  • Configurable potential/pipeline tracking covers deal value and stage progression alongside fulfillment data.

Weaknesses

  • No publicly documented API, developer portal, or OpenAPI specification was found.
  • Per-feature pricing accumulates unpredictably as teams enable additional modules.
  • Minimal public documentation and thin online presence makes independent evaluation and support discovery difficult.
  • Customisable-per-deployment schema means no reliable standard field set across customer accounts.
  • No published free tier or free trial available to test before commitment.
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. 2 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 Black Ice CRM and Nutshell.

  • Object compatibility

    B

    2 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

    Black Ice CRM: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Black Ice CRM 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 Black Ice CRM to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Migrations under 2,500 total records (Accounts, Contacts, Leads, Deals) with no active Quotes, Orders, or Invoices modules complete in one to three weeks. Migrations with the full Black Ice sales cycle active (Quotes, Orders, Invoices, Products with stock data) and custom fields on each object move to three to six weeks because of the dependency sequencing, semantic mapping for Order-Invoice objects, and the required pre-migration field audit. Timeline assumes a confirmed export method and active customer participation in scoping and reconciliation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Black Ice CRM.
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