Migrate from Gauss Box CRM & Sales to Salesforce Sales Cloud

Gauss Box Leads with a work status and assigned team member map to Salesforce Lead records. We preserve the Gauss Box lead-to-contact link by retaining the original Gauss Box Lead ID as a custom external ID field (gauss_box_lead_id__c) for reference and deduplication. The Lead's assigned team member maps to Salesforce OwnerId via email lookup against the destination User table. Any Gauss Box Lead that has already been converted to a Contact before migration is flagged to skip the Lead creation and appears only as a Contact with Account linkage.

Gauss Box unlimited Contacts map to Salesforce Contact records. Standard fields (Name, Email, Phone, MailingAddress) migrate directly. Custom attributes discovered in the account's Gauss Box attribute sets migrate as Salesforce custom fields (text, picklist, date, or number type depending on Gauss Box field type). Contacts without an Account link are held in a queue for Account creation before Contact import resumes to satisfy the AccountId Lookup requirement.

Gauss Box Organizations (unlimited per account) map to Salesforce Account. Organization name maps to Account Name, industry maps to Industry picklist, and D&B business intelligence data fields (credit rating, employee count, revenue range) map to custom Account fields we create during schema design. Address fields migrate to BillingAddress. Account is imported before Contact so that AccountId is available at Contact insert time. If a Contact has multiple Organization associations in Gauss Box (rare), we attach it to the primary Account and flag the secondary association for manual review.

Gauss Box Deals map to Salesforce Opportunity. Deal stage name maps to Salesforce StageName, Deal value maps to Amount, owner maps to OwnerId, and product associations map to OpportunityLineItem after Pricebook resolution. Gauss Box budget and custom deal attributes migrate as custom Opportunity fields. Closed-Lost and Closed-Won statuses from Gauss Box map to Salesforce standard stage names with the original Gauss Box deal outcome preserved in a custom field gauss_box_deal_status__c.

Gauss Box configurable stage names (unique per account) require mapping to Salesforce StageName values. We enumerate every active Gauss Box deal stage during discovery and create matching Salesforce stage values in the destination org's Sales Process before migration. Stage probability percentages migrate from Gauss Box to Salesforce StageProbability with rounding to Salesforce's integer constraint. Stage order is preserved via StageSortOrder.

Gauss Box uses a single pipeline per account with configurable stages. If the customer uses multiple distinct sales processes (e.g., one for direct sales and one for channel), we map each to a Salesforce Record Type on Opportunity with its own Sales Process whitelisting the relevant stage values. Page Layouts are assigned per Record Type so that sales reps see only the fields relevant to their process.

Gauss Box Activities linked to Deals migrate to Salesforce Task records. Activity type, timestamp, and description map to Task Subject, ActivityDate, and Description. The Task WhatId points to the migrated Opportunity. If the Gauss Box Activity type is a call, we set TaskSubtype = Call and map any call disposition to a custom Task field. Activity timestamp ordering is preserved by setting ActivityDate to the original Gauss Box timestamp.

Gauss Box Activities linked directly to Contacts (not via a Deal) migrate to Salesforce Task with WhoId pointing to the migrated Contact and no WhatId. These represent interactions not tied to a pipeline opportunity and are preserved as standalone Tasks on the Contact timeline.

Gauss Box automatic reminders and smart notifications tied to Deal and Activity records are embedded in parent record metadata and are not independently exportable as rows. We extract what is present in the CSV, flag records with active reminders that will not carry over as standalone records, and document the open reminder count per Deal so the customer's admin can recreate priority reminders in Salesforce Flow post-migration. This is not a data loss gap — it is a feature gap we surface explicitly.

Gauss Box Products with category, type, price, and sale tax configuration map to Salesforce Product2 records. Product name maps to Name, product code maps to ProductCode, and the base price creates a Standard PricebookEntry in the destination org's default Pricebook. Gauss Box tax configuration maps to a custom field on Product2 since Salesforce does not have a native tax rate object at the product level.

Gauss Box Deals carry product associations that map to Salesforce OpportunityLineItem at migration time. We resolve the Pricebook2 reference (using the default Pricebook), the Product2 reference (via external ID from the Product migration phase), and the parent Opportunity (via the Deal-to-Opportunity mapping). Quantity and pricing migrate from Gauss Box deal-product line items.

Gauss Box stores documents per record with access permissions. We extract files from the Gauss Box export package and re-attach them to the corresponding migrated Salesforce record (Contact, Account, or Opportunity) via ContentVersion (file content) and ContentDocumentLink (record linkage). File metadata and permissions are preserved as Salesforce sharing settings on the ContentDocument. Document versions migrate as separate ContentVersion records linked to the same ContentDocument.

Gauss Box user accounts referenced on Leads, Contacts, Deals, and Activities map to Salesforce User records by email address match. Any Gauss Box Owner without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Owner count is audited during scoping to prevent surprise user licensing costs in the Salesforce destination org.

Gauss Box attribute sets define custom fields on Contacts, Organizations, Deals, and Products that are not standardized across accounts. We run a mandatory discovery phase enumerating every active attribute set before schema design. Each custom attribute becomes a Salesforce custom field (Text, Number, Date, Checkbox, or Picklist) on the equivalent standard object. Fields that cannot be typed directly (e.g., Gauss Box multi-select attributes) map to Salesforce multi-select picklists. Attribute sets unique to one Gauss Box account but not present in others require custom field creation before data import.