Migrate from Gauss Box CRM & Sales to Microsoft Dynamics 365 Sales

Gauss Box Organization records map directly to Dynamics 365 Account. The Organization name, industry, size, D&B data fields (if enriched in Gauss Box), and address fields map to Account name, industry, numberofemployees, and address fields. D&B creditworthiness data does not have a native Dynamics 365 field and migrates to a custom field dnb_credit_rating__c or similar if the customer licenses D&B Enrichment for Dynamics. Organization is created first so that Contact records can satisfy the AccountId lookup during import.

Gauss Box Contact records map to Dynamics 365 Contact with firstname, lastname, emailaddress1, telephone1, and address fields preserved directly. Any custom attributes defined on the Gauss Box Contact attribute set become Dynamics 365 custom fields pre-created during schema design. We resolve the parent Organization link by matching Gauss Box organization_id to Account.accountid using a staging lookup table built during the Organization migration phase.

Gauss Box Lead records map to Dynamics 365 Lead. The lead's work status (active, converted, inactive) maps to lead.statuscode and lead.statecode. We preserve the Gauss Box lead-to-contact relationship by mapping the original Lead ID to a custom field original_lead_id__c on the destination Lead. Assigned team member maps to OwnerId via email lookup against the Dynamics 365 User table. Lead status values from Gauss Box translate to Dynamics 365 LeadStatus codes (New, Contacted, Qualified, Unqualified) configured during schema setup.

Gauss Box Deal records map to Dynamics 365 Opportunity. The dealstage property maps to Opportunity.stagecode and stepname within the configured Sales Process. Deal value maps to Opportunity.estimatedvalue, and budget and product associations map to custom fields or to OpportunityLineItem records created after Products are migrated. Pipeline stage names are configurable per Gauss Box account, so we map each unique Gauss Box stage name to a corresponding Dynamics 365 Opportunity Stage value during schema discovery. Owner resolution uses email-to-User lookup identical to the Contact mapping.

Each unique Gauss Box deal pipeline becomes a Microsoft Dynamics 365 Sales Process attached to a Record Type on Opportunity. We enumerate all Gauss Box pipeline stage names during discovery and create matching stagecode values in Dynamics 365 with corresponding probability percentages. If the customer has multiple Gauss Box pipelines, each becomes a separate Record Type with its own Sales Process to isolate stage values per line of business.

Gauss Box Activities (interactions, reminders, notes) map to Dynamics 365 Activity records. We classify by Gauss Box activity type: calls become PhoneCall, meetings become Appointment, tasks become Task, and notes become the Dynamics 365 Note entity linked via InstantId to the parent Contact or Opportunity. The parent object link (Deal or Contact) migrates as WhatId and WhoId respectively. Timestamps preserve as ActivityDate and ActualEnd. We flag Gauss Box automatic reminder data that cannot be independently exported and document those counts for manual recreation.

Gauss Box Product catalog records (name, category, type, price, sale tax configuration) map to Dynamics 365 Product. Product name maps to Product.name, product code maps to Product.productnumber, and price maps to the Standard Price Book entry created during migration. Sale tax configuration from Gauss Box does not have a native Dynamics 365 field and migrates to a custom field tax_configuration__c. Products are migrated before Deals so that deal-product associations resolve correctly via OpportunityLineItem.

Gauss Box documents stored per record extract as files and re-attach to the corresponding migrated Account, Contact, or Opportunity record in Dynamics 365 as Annotation records with file attachments. We preserve filename and any metadata available from the Gauss Box export. Document access permissions do not have a native Dynamics 365 equivalent; the destination inherits Dynamics 365's own field-level security model.

Gauss Box attribute sets on Contacts are enumerated during discovery and mapped to Dynamics 365 custom fields on the Contact entity. Field type mapping follows standard rules: text fields become nvarchar, numbers become int or decimal, dates become datetime, and multi-value attributes become nvarchar (comma-separated) or custom option set if the value set is bounded. Custom fields are created via Dynamics 365 solution before any Contact records are imported.

Gauss Box user accounts assigned as Deal owners, Lead owners, or Activity owners map to Dynamics 365 User records via email address resolution. Any Gauss Box user without a matching Dynamics 365 User record enters a reconciliation queue for the customer to provision. Inactive Gauss Box accounts are flagged but not provisioned in Dynamics 365 unless the customer requests preservation of historical assignment.