Migrate from Black Ice CRM to Salesforce Sales Cloud

Black Ice Accounts (companies) map directly to Salesforce Account. Company name becomes Name, address fields map to BillingAddress and ShippingAddress compound fields. Black Ice Accounts serve as the parent for all Contact records, so Account is the first object loaded in every migration to satisfy the Contact.AccountId lookup. We resolve any cross-account duplicates using company name and domain as dedupe keys. Address formatting differences (UK postcodes vs US address standards) are handled during the transform step using field-level normalization.

Black Ice Contact records map to Salesforce Contact with the Contact.AccountId lookup resolved at load time against the Account records loaded in the preceding step. Black Ice stores phone, email, job title, and any custom fields; these map to typed Salesforce fields (Phone, Email, Title) or custom fields created during schema design. Contact deduplication uses Email as the unique key. If Black Ice Contact records lack an Account association, we flag them for the customer's admin to confirm whether they should map to an existing Account or create a standalone Contact.

Black Ice Lead records map to Salesforce Lead. Unlike HubSpot's unified Contact model, Black Ice appears to maintain Leads as separate from Accounts/Contacts within its data model. We migrate them to Salesforce Lead with IsConverted set to false initially. Any Lead that represents an existing customer account is flagged for manual review before migration to avoid creating duplicate Lead records for accounts already in Salesforce Account. Lead Status and Lead Source fields are mapped against Salesforce picklist values or extended with custom picklist values if the source values have no direct Salesforce equivalent.

Black Ice's Potential object holds pipeline stage and deal value data that maps to Salesforce Opportunity. The stage name, estimated value, and close date transfer directly. Black Ice stage names are deployment-specific, so we create a Salesforce Sales Process and StageName picklist that mirrors the source stage sequence during schema design before migration begins. Deal owner maps to Salesforce OwnerId via the User email resolution step. If Black Ice stores multiple pipelines, we map each to a separate Salesforce Record Type on Opportunity with its own Sales Process.

Black Ice Quotes with header fields and line items map to Salesforce Quote, available natively from Sales Cloud Professional. Quote header fields (quote date, expiration, status) map to QuoteNumber, expirationDate, and Status. Line items map to a separate QuoteLineItem step after the parent Quote and related Opportunity are created. We preserve the Quote-to-Opportunity link so the quote appears in the Opportunity's Quotes related list post-migration. If Black Ice quotes include pricing in multiple currencies, we apply the appropriate conversion using exchange rates current at migration date.

Black Ice Orders are derived from accepted Quotes and carry line items linked to Products. We map Orders to Salesforce Order with OrderNumber, Status, EffectiveDate, and AccountId resolved at load time. Line items migrate after Order creation as OrderProduct records, with Product2 and Pricebook2 references resolved. Black Ice's automatic stock reduction on order creation does not transfer as a live process; we carry forward the order records and let the customer's Salesforce admin configure inventory management through an AppExchange app or custom build post-migration.

Black Ice Invoices linked to Orders map to Salesforce Invoice, available from Sales Cloud Professional. We preserve the Invoice-to-Order relationship using Salesforce's原生 OrderId field on Invoice. Payment status from Black Ice transfers to InvoiceStatus. If Black Ice stores invoice PDFs, we attach them as ContentDocument records linked to the Invoice. Note that Salesforce Invoice is designed for usage-based or subscription billing; if the customer's Black Ice invoices are transactional one-offs, the customer's admin should validate invoice layout and print formatting in Salesforce after migration.

Black Ice Product records map to Salesforce Product2 with Standard Price Book entries created during import. Product name maps to Name, SKU from Black Ice maps to ProductCode, and current stock quantity maps to a custom field qty_in_stock__c because Salesforce Product2 does not have a native inventory field. Reorder threshold values from Black Ice's automated inventory alerts migrate to a custom field reorder_threshold__c for the customer's inventory management setup to reference. We flag that live stock decrementing requires post-migration configuration through Salesforce's inventory management apps or a custom Flow.

Black Ice line items on Quotes and Orders map to Salesforce OpportunityLineItem, QuoteLineItem, and OrderProduct depending on the parent object. We resolve the Pricebook2 reference, the Product2 reference, and the parent Opportunity or Order ID at migration time. Quantity, UnitPrice, and any discount percentage migrate directly. Line items are loaded after their parent objects to satisfy the required lookups.

Black Ice stock levels and reorder thresholds migrate as custom fields on Product2 rather than as a separate inventory object. The current stock quantity becomes qty_in_stock__c and the alert threshold becomes reorder_threshold__c. This is a point-in-time snapshot; ongoing stock changes are not synced automatically. The customer should configure a periodic reconciliation process or integrate an inventory management AppExchange solution (such as Avantior, IN-SYNCH, or a custom build) post-migration if live stock tracking is required in Salesforce.

Black Ice's fully customisable modules mean every deployment has custom fields not present in other Black Ice instances. We create a custom field audit step during discovery — either via a sample export or a screen walkthrough — to identify all active custom fields before building the Salesforce schema. Each Black Ice custom property is mapped to a typed Salesforce custom field (Text, Number, Date, Picklist, Checkbox, etc.) with the same API name convention plus __c suffix. Custom picklist values from Black Ice are added to Salesforce picklist definitions before data load to avoid validation rule rejections.

Black Ice user records (owners on Leads, Accounts, Contacts, Deals, Orders, Invoices) map to Salesforce User records. We resolve owners by email match against the destination Salesforce org's User table during migration. Any Black Ice owner without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId lookups on Accounts, Contacts, Opportunities, and Orders are resolved at load time using the validated User map.