CRM migration
Field-level mapping, validation, and rollback between Black Ice CRM and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Black Ice CRM
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
7 of 8
objects map 1:1 between Black Ice CRM and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3-4 weeks
Overview
Black Ice CRM and Microsoft Microsoft Dynamics 365 Sales use different structural models for the sales cycle. Black Ice CRM stores Accounts and Contacts as separate objects, tracks pipeline stages through a Potential/Pipeline object, and links Quotes to Orders to Invoices as a linear chain. Microsoft Dynamics 365 Sales uses Accounts, Contacts, and Opportunities as its primary objects with a configurable opportunity pipeline, and stores Quotes, Orders, and Products in separate but related entities. We resolve these schema differences during a pre-migration field audit, map Black Ice's customisable modules to typed Dynamics 365 entities, and run the export through Black Ice's built-in export utility rather than an API. Custom workflows, automations, and picking-list documents are documented separately for the customer's admin to rebuild. Microsoft Dynamics 365 Sales does not migrate as a simple record copy; the structural mapping work is the core of what we deliver.
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.
Source platform
Black Ice CRM platform overview
Scorecard, SWOT, gotchas, and pricing for Black Ice CRM.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Black Ice CRM object lands in Microsoft Dynamics 365 Sales , 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
Accounts
Microsoft Dynamics 365 Sales
Account
1:1Black Ice Accounts (companies) map directly to Microsoft Dynamics 365 Sales Account. The company name becomes Account Name, and address fields map to Address composite fields or individual address line fields in Dataverse. We preserve the account-contact relationship by importing Accounts before Contacts so that AccountId lookups are satisfied at the moment of Contact insert. Any Black Ice custom company fields identified in the pre-migration audit are created as custom Account fields in the destination org before import.
Black Ice CRM
Contacts
Microsoft Dynamics 365 Sales
Contact
1:1Black Ice Contact records map to Microsoft Dynamics 365 Sales Contact with first name, last name, email, phone, and custom fields preserved. We resolve the Contact-to-Account relationship using a match on email domain or an explicit Black Ice company association field. If the Black Ice deployment stores contact roles (decision-maker, influencer, buyer) as custom fields, we map these to the Dynamics 365 Contact Relationship or a custom picklist field.
Black Ice CRM
Leads
Microsoft Dynamics 365 Sales
Lead
1:1Black Ice Leads map to Microsoft Dynamics 365 Sales Lead. The Black Ice lead status field maps to Lead Status in Dynamics 365, and any lead source or score custom fields migrate to custom Lead fields. We flag any Black Ice deployment where Leads and Contacts are used interchangeably; in that case, we present the customer with a merge-versus-split recommendation during scoping before the migration mapping is finalised.
Black Ice CRM
Products
Microsoft Dynamics 365 Sales
Product (Product2)
1:1Black Ice Products (name, SKU, price, stock levels) map to Dynamics 365 Product2 records. SKU maps from Black Ice's product code field, and unit price maps to Standard Price Book entries created during import. If the customer uses the Products module for inventory tracking, current stock quantities migrate as a custom field on Product2 since Microsoft Dynamics 365 Sales does not manage live inventory; the customer's admin configures a separate inventory management approach (Business Central, spreadsheet, or third-party) post-migration.
Black Ice CRM
Quotes
Microsoft Dynamics 365 Sales
Quote
1:1Black Ice Quotes map to Dynamics 365 Quote with header fields (quote number, date, validity, total) and line items. Quote line items map to QuoteLineItem with Product2 reference, quantity, and UnitPrice resolved at migration time. The originating Account and Contact are linked via the Quote's CustomerId and ContactId fields. Quote status (Draft, Sent, Accepted, Lost) maps to the Dynamics 365 statuscode field.
Black Ice CRM
Orders
Microsoft Dynamics 365 Sales
Sales Order (OrderProduct)
1:1Black Ice Orders map to Microsoft Dynamics 365 Sales Order or Invoice depending on the order lifecycle stage. Order line items map to OrderProduct with the Product2 reference resolved. In Microsoft Dynamics 365 Sales standalone, Orders are linked to Quotes; in a combined Sales and Business Central deployment, Orders sync via the Dataverse-Business Central integration. We confirm whether Business Central is in scope during discovery.
Black Ice CRM
Potential / Pipeline
Microsoft Dynamics 365 Sales
Opportunity
1:1Black Ice's Potential object maps to Microsoft Dynamics 365 Sales Opportunity. Stage name and estimated value migrate from Black Ice's pipeline tracking fields to Opportunity StageName and Amount. The Black Ice pipeline assignment becomes an Opportunity Record Type or Sales Process in Dynamics 365, which we configure before migration. Closed-Lost and Closed-Won outcomes from Black Ice map to the corresponding Dynamics 365 stage transitions.
Black Ice CRM
Custom Fields (per module)
Microsoft Dynamics 365 Sales
Custom Fields (on Account, Contact, Opportunity, etc.)
lossyBlack Ice CRM's fully customisable modules mean every deployment has custom fields that do not appear in a standard installation. We require a pre-migration field audit — a sample export or a guided screen walkthrough — to document the exact schema in use. Each custom field is created in Dynamics 365 with the appropriate field type (text, number, picklist, date, boolean) before any data import. Custom field mapping is the most variable part of a Black Ice migration and is resolved during the discovery phase, not assumed from any standard schema.
| Black Ice CRM | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Accounts | Account1:1 | Fully supported | |
| Contacts | Contact1:1 | Fully supported | |
| Leads | Lead1:1 | Mapping required | |
| Products | Product (Product2)1:1 | Mapping required | |
| Quotes | Quote1:1 | Mapping required | |
| Orders | Sales Order (OrderProduct)1:1 | Mapping required | |
| Potential / Pipeline | Opportunity1:1 | Fully supported | |
| Custom Fields (per module) | Custom Fields (on Account, Contact, Opportunity, etc.)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.
Black Ice CRM gotchas
Per-feature pricing obscures true migration scope
No publicly documented API schema or rate limits
Fully customisable modules create unpredictable schema
Picking list and stock alert data may not export cleanly
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Discovery and export method confirmation
We begin with a discovery call to identify all active Black Ice modules (Leads, Accounts, Contacts, Quotes, Orders, Invoices, Products, Stock, Potential/Pipeline), confirm the data volumes per module, and establish the available export method. If Black Ice's built-in export utility produces a usable format (CSV, Excel, XML), we work with that directly. If it produces PDF or formatted reports only, we flag this as a data reconstruction requirement and revise the migration scope accordingly. We also review any available database access or backup files as an alternative export path.
Field-level schema audit
We require a sample export from Black Ice CRM covering at least one representative record per active module, or a guided screen walkthrough of the field structure in each module. This allows us to document the actual schema in use — standard fields plus any custom fields — and map them to typed Dynamics 365 fields before migration. The audit output is a field mapping spreadsheet reviewed and approved by the customer's admin before any data moves. This step is the primary risk mitigator for Black Ice's per-deployment customisation variability.
Microsoft Dynamics 365 Sales environment preparation
We set up the Microsoft Dynamics 365 Sales destination environment by creating the entities and custom fields identified in the field audit, configuring the Opportunity pipeline with stage names and probabilities that mirror the Black Ice potential/pipeline structure, setting up Product2 records and the standard Price Book, and assigning security roles. We work in a Dynamics 365 Sandbox first to validate the schema and mapping before touching production data.
Data cleansing and import scripting
We profile the Black Ice export data for duplicates, missing required fields, inconsistent date formats, and incomplete records. We apply a cleansing script to standardise formats, deduplicate Accounts and Contacts by name and email, and flag any records that cannot be imported without manual correction. Cleansed data is staged in CSV format ready for Dynamics 365 Bulk API ingestion.
Production migration in dependency order
We run the migration in record-dependency order: Products (resolved first as the product catalogue reference), Accounts, Contacts (with AccountId resolved), Leads, Opportunities (with AccountId and OwnerId resolved and stage mapped to the configured pipeline), Quotes (linked to Account, Contact, and Products), Orders (linked to Quotes), and engagement history (Tasks, Notes, and any other activity records present in the Black Ice export). Each phase emits a row-count reconciliation report before the next phase begins.
Cutover and workflow rebuild handoff
We freeze Black Ice CRM writes during the cutover window, run a final delta import of any records modified during the migration window, then redirect the team to Microsoft Dynamics 365 Sales as the system of record. We deliver the automation inventory document covering any Black Ice workflow or notification rules that require rebuilding in Microsoft Dynamics 365 Sales via Power Automate or custom workflow. We support a one-week post-cutover reconciliation window for data discrepancies. We do not rebuild Black Ice workflows inside the migration scope.
Platform deep dives
Black Ice CRM
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Black Ice CRM and Microsoft Dynamics 365 Sales .
Object compatibility
2 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
Black Ice CRM: Not publicly documented.
Data volume sensitivity
Black Ice 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 Black Ice CRM to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Black Ice CRM to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Black Ice CRM
Other ways to arrive at Microsoft Dynamics 365 Sales
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.