Migrate from Gauss Box CRM & Sales to Freshsales

Gauss Box Organization records map to Freshsales Account. Organization name, industry, size, address fields, and D&B data fields (creditworthiness and risk indicators) migrate directly. D&B enrichment data present in Gauss Box carries over as read-only fields; Freshsales does not include live D&B integration on the Estate and Forest tiers by default, so the customer may choose to re-enrich accounts post-migration using a Freshworks marketplace enrichment app. Account is created before any Contact import so that the account_id lookup is satisfied at Contact insert time.

Gauss Box Product catalog records (name, category, type, price, sale tax configuration) map to Freshsales Product. ProductCode maps from Gauss Box internal product identifier. Sale tax configuration from Gauss Box maps to Freshsales Tax group if the Forest tier is selected; lower tiers handle tax at the deal level. We reassign products to Deals at the destination based on the stored deal-product associations from Gauss Box.

Gauss Box unlimited person Contacts map to Freshsales Contact. All standard fields (name, email, phone, address) migrate directly. Any custom attributes from the Gauss Box attribute-set system are enumerated during discovery and pre-created as custom fields in Freshsales before Contact import. The Contact-account lookup resolves to the migrated Account ID.

Gauss Box Lead records map to Freshsales Lead. The Gauss Box work status property maps to Freshsales Lead Status as a dropdown value. Assigned team member maps to Freshsales Owner by email resolution. Gauss Box lead-to-contact links are preserved by mapping the Gauss Box Lead ID alongside the corresponding Gauss Box Contact ID in a custom field (e.g., gb_original_lead_id__c) so the relationship is auditable after migration. Freshsales Lead-to-Contact conversion field mapping is configured post-migration for the customer's admin to define which lead fields carry into Contact, Account, and Deal at conversion time.

Gauss Box Deals map to Freshsales Deal. The deal stage maps to Freshsales Deal Stage, with the stage name mapped to the destination pipeline's stage schema at migration time. Deal value, owner, and product associations (line items) migrate. If the customer has configured multiple pipelines in Gauss Box, each becomes a separate pipeline in Freshsales. Budget and custom fields map from the Gauss Box attribute set. Closed-Lost and Closed-Won reasons from Gauss Box custom fields map to Freshsales Deal custom fields if defined.

Gauss Box Activities (interactions linked to Deals and Contacts, including automatic reminders) map to Freshsales Task records. Activity type, timestamp, description, and parent object link migrate. Activity timestamp preserves the original date for activity timeline ordering. Note that Gauss Box system-generated automatic reminders embedded in parent record metadata are not independently exportable as separate rows; we extract what appears in the CSV and flag records with active reminders that will not carry over as standalone task records. The customer documents open reminder counts before migration to recreate priority reminders in Freshsales.

Gauss Box documents stored per record with access permissions extract as files and re-attach to the corresponding migrated record in Freshsales (Contact, Account, or Deal) preserving filename and stored metadata. Document versions are not supported in Freshsales standard attachments; we attach the latest version and note any earlier versions that should be preserved manually if version history is required.

Deals, Leads, and Contacts carry owner assignments tied to Gauss Box user accounts. We extract all distinct owner email addresses and resolve them against the Freshsales User directory by email match. Any owner without a matching Freshsales User is flagged in a reconciliation queue for the customer's admin to provision before record import resumes. We do not auto-provision users because Freshsales assigns role and territory at provisioning time, which requires admin judgment.

Gauss Box attribute sets allow account-specific custom fields on Contacts, Organizations, Deals, and Products. These fields are not standardized across accounts and require a mandatory discovery phase before mapping. We enumerate every active attribute set during scoping, pre-create the corresponding custom fields in Freshsales with appropriate field types (text, number, date, picklist), and then map each Gauss Box attribute to the Freshsales field during migration. Fields that exist only in Gauss Box and have no Freshsales equivalent are created as new custom fields; the customer chooses naming conventions during discovery. This is the highest-risk step for data quality if skipped.