Migrate from Black Ice CRM to Twenty CRM

Black Ice Accounts (companies) map directly to Twenty Company records. We extract company name, address fields, phone, website, and any custom fields from the Accounts module. Company is the first object imported because it is the 'one' side of the one-to-many relationship with People (Contacts). The deduplication key during import is the company name or domain if present.

Black Ice Contact records map to Twenty Person objects. We preserve the contact-to-account relationship by resolving the Black Ice company association to a Twenty Company ID at import time. Fields including name, email, phone, job title, and any custom contact properties migrate directly. If Black Ice stores contacts without a company link, those Person records import without a Company association and the customer's admin can link them post-migration.

Black Ice Quotes map to Twenty Opportunity records. Quote header fields (quote number, date, status, total value) become Opportunity fields. Quote line items are related to the Opportunity via the opportunityId relationship in Twenty. We map the Black Ice quote status (Draft, Sent, Accepted, Declined) to a Twenty Opportunity custom field rather than assuming a direct stage mapping, as quote lifecycle differs from pipeline opportunity lifecycle.

Black Ice Orders, which are derived from accepted Quotes, map to Twenty Opportunity records with a distinct status or a separate custom field (order_status__c) indicating they originated as orders rather than pipeline opportunities. Line items from the Black Ice Order migrate as OpportunityLineItem equivalents in Twenty. We preserve the Black Ice order-to-invoice relationship by noting the linked invoice identifier on the Opportunity record.

Black Ice Invoices are linked to Orders and carry payment status, invoice number, and line items. Twenty CRM does not have a native invoice object. We migrate invoice data as a structured custom field set on the related Opportunity (or as a separate custom Invoice object created via Twenty's metadata API if the customer requires it). Payment status and invoice number become custom fields; line items are noted in a text summary field. The customer's admin configures any downstream accounting integration (Stripe, QuickBooks, Xero) post-migration.

Black Ice Product records (name, SKU, price, stock level) map to Twenty Standard Objects with fields for name, sku, price, and stock_quantity__c as a custom field. Product associations to Orders migrate as child records linked via the Opportunity lookup. SKU maps from Black Ice's product code field.

Black Ice stock levels and reorder thresholds migrate as custom fields on the Product Standard Object (stock_quantity__c and reorder_threshold__c). Twenty CRM has no native inventory management module, so live stock quantities and automated alerts do not replicate — the customer's admin sets up a post-migration inventory process or external tool. Picking list documents are application-generated derived data and do not migrate as primary records.

Black Ice Potential records track pipeline stage and deal value. They map to Twenty Opportunity records with stage name and amount fields. We extract the Black Ice pipeline stage name and map it to a corresponding Twenty pipeline stage or a custom pipeline field if the source stage names are non-standard. Estimated value migrates as the Opportunity amount.

Black Ice Leads (the primary entry point in the sales cycle) map to Twenty Person records that do not have a linked Company. We flag these at migration time as unqualified or pre-qualification records. If the customer uses a separate Leads module distinct from Contacts in Black Ice, we maintain the distinction by adding a custom field lead_source_module__c on the Person record. The customer's admin in Twenty reviews and links to a Company or converts to a Pipeline Opportunity as appropriate.

Black Ice CRM's fully customisable modules mean custom fields vary by deployment. During the pre-migration field audit, we document every active custom property across Accounts, Contacts, Quotes, Orders, Products, and Potentials. We then use Twenty's /metadata API to pre-create each custom field before data import begins, matching field types (text, number, date, picklist) from the Black Ice sample export. Custom fields on Black Ice's custom modules migrate as custom fields on the corresponding Twenty Standard Object or as fields on a custom object created via metadata API.