Migrate from Gauss Box CRM & Sales to Zoho CRM

Gauss Box Leads map to Zoho CRM Leads with the full set of lead fields (name, email, phone, source, status, assigned team member) transferred. The work status property from Gauss Box maps to Zoho Lead Status. We preserve the original Gauss Box Lead ID in a custom field gbox_lead_id__c for traceability. If the customer uses a lead-conversion process, the Zoho Lead is set up for conversion to Contact with Account creation during migration so that the existing Gauss Box lead-to-contact link is approximated.

Gauss Box Persons (unlimited contacts) map directly to Zoho CRM Contacts. Standard fields (name, email, phone, address, organization link) map 1:1. Custom attributes defined in the Gauss Box attribute set for Contacts are enumerated during discovery and recreated as Zoho custom fields on the Contact module before import. Any D&B enrichment fields stored on the Gauss Box Contact are flagged for manual review or replacement via Zoho DataBoost enrichment if the customer has that add-on.

Gauss Box Organizations map to Zoho CRM Accounts with the Organization name, industry, size, D&B data fields, and address fields transferred directly. D&B business intelligence enrichment from Gauss Box maps to Zoho Account fields if the customer licenses Zoho DataBoost, otherwise it is flagged as a manual-enrichment candidate. Account is imported before Contact so that the Account-Contact lookup is resolved at Contact insert time.

Gauss Box Deals map to Zoho CRM Deals with stage, owner, value, budget, and product associations preserved. Pipeline stage names are configurable per Gauss Box account, so we map them to Zoho's Deal Stage field during import, creating new Stage values in Zoho that match the source naming. The Gauss Box deal-product associations migrate as Line Items attached to the Zoho Deal using the Product Name lookup.

Gauss Box Activities split into Zoho Tasks (for calls, tasks, and automatic reminders) and Zoho Events (for calendar meetings). Activity type determines the target object: type_interaction maps to Task with description; type_meeting maps to Event with start/end time and location; type_reminder maps to Task with a custom field reminder_flag__c set to true and priority set to High. The parent object link (Deal or Contact) migrates as a WhatId or WhoId lookup in Zoho.

Gauss Box Products map to Zoho CRM Products with name, category, type, unit price, and tax information preserved. The Gauss Box sale tax configuration maps to Zoho's Tax structure. Products are imported before Deals so that Line Item associations resolve correctly. Gauss Box does not support tiered or volume-based pricing rules natively, so there are no complex pricing rules to transform.

Gauss Box per-record documents and files migrate to Zoho CRM Attachments. We extract files from Gauss Box CSV export or file system, pair each file with its parent record using the Gauss Box document metadata, and reattach them to the corresponding migrated record in Zoho using the Zoho Attachments API. File metadata (filename, upload date, access permissions) is preserved where available. Note that Gauss Box document templates and version history do not migrate; we document the count of templated documents for the customer's admin to recreate.

Deals, Leads, and Activities in Gauss Box carry owner assignments tied to Gauss Box user accounts. We resolve owners by email match against the Zoho CRM destination User directory. Owners without a matching Zoho User go to a reconciliation queue for the customer's admin to provision. Inactive Gauss Box accounts are flagged to prevent new user creation for users who should not have Zoho access.

Gauss Box attribute sets define custom fields on Contacts, Organizations, Deals, and Products that vary by account. We enumerate every active custom attribute during discovery, determine its data type, and create the equivalent Zoho custom field on the corresponding module before any data is imported. Fields that exist only in Gauss Box must be created as new Zoho custom fields; if a field name already exists in Zoho with a different type, we flag the conflict and propose a renamed destination field with a note.

Gauss Box Organizations may carry D&B enrichment fields (creditworthiness, risk indicators, firmographics) that were added during the D&B enrichment step. These custom fields on the Organization object are enumerated during discovery and mapped to Zoho Account custom fields. If the customer licenses Zoho DataBoost, we recommend a post-migration enrichment run to refresh D&B data in Zoho rather than carrying stale enrichment records across.

Gauss Box smart notifications are embedded in Deal and Activity metadata rather than stored as independent records. We extract any visible reminder dates and notification counts, map them to Zoho Tasks with a custom field notification_source__c set to 'GaussBox', priority set to High, and the original reminder date stored as the Task Due Date. Records with active reminders that cannot be extracted from metadata are flagged in the reconciliation report for manual recreation.