Migrate from Gauss Box CRM & Sales to Twenty CRM

Gauss Box Organizations (company records) map directly to Twenty Company records. The Organization name, industry, size, D&B data fields (if the Gauss Box account had D&B enrichment active), and address fields map to the corresponding Twenty Company fields. Organization is loaded first because Persons and Deals carry foreign-key references to it. The Twenty Company API accepts name, domain, employees, industry, and address as typed fields. Any custom attributes defined on the Organization object in Gauss Box's attribute-set system are enumerated during discovery and pre-created as custom fields on the Twenty Company object before migration.

Gauss Box Products (name, category, type, price, sale tax configuration) map to Twenty Products if the Twenty instance has the Products feature enabled, or to a custom Product object if the standard feature is not active. ProductCode from Gauss Box maps to the sku field. We reassign products to Deals at the destination using the stored deal-product associations. Tiered pricing and volume discount rules that were custom Gauss Box configurations become custom fields on the destination Product record.

Gauss Box Persons map directly to Twenty Person records. Name, email, phone, address, and any role or title field map to the corresponding Twenty Person fields. Persons carry a link to their parent Organization, which is resolved by matching the Organization's external ID (we assign a stable UUID during Organization migration) against the Organization field on the Person record during migration. All account-specific custom attributes on the Gauss Box Person object are pre-created as custom fields on Twenty Person before the Person batch load.

Gauss Box Leads carry a work status, assigned team member, and a link to a corresponding Person. We map Leads to Twenty Person records with the work status preserved in a custom field (lead_work_status__c). If Twenty is configured with a dedicated Lead object (via custom object definition), unqualified Leads map to the Lead object and converted Leads map to Person. The lead-to-person link is preserved by recording the original Gauss Box lead_id in a custom field on the destination Person for audit and reconciliation.

Gauss Box Deals map to Twenty Opportunity records. Deal fields (stage, owner, value, budget, product associations, close date) map to the corresponding Opportunity fields. Pipeline stage names are configurable per Gauss Box account, so we enumerate the active stage set during discovery and map it to Twenty's Opportunity stage field, creating any missing stage values in Twenty before migration. Deal-product associations are resolved by looking up the migrated Product UUIDs against the imported product records. Owner assignment uses the Gauss Box owner's email address, resolved against the Twenty user directory during migration.

Gauss Box Activities (interactions linked to Deals and Persons) map to Twenty Task records for standard activities and Event records for meetings and calendar events. Activity type, timestamp, description, and parent object link (person or deal) migrate directly. Gauss Box ties automatic reminders to Activity records, but these system-generated reminders are often embedded in the parent record metadata rather than exported as independent rows. We extract what is present, flag records with active reminders that will not carry over as discrete activities, and recommend the customer document open reminder counts before migration so they can recreate priority reminders in Twenty.

Gauss Box stores documents per record with access permissions in its document management module. We extract files with their filenames and any stored metadata, then re-attach them to the corresponding migrated Company or Person record in Twenty. File metadata (created date, modified date, access level) migrates as attachment metadata fields. Access permissions that existed in Gauss Box's document module do not transfer to Twenty's attachment model and must be reconfigured by the customer's admin post-migration if permission-scoped document access is required.

Gauss Box attribute sets allow each account to define custom fields on Persons, Organizations, Deals, and Products. These fields are not standardized across accounts. We run a mandatory discovery phase to enumerate every active attribute set before mapping begins. Each discovered custom field is pre-created in Twenty with a matching field type (text, number, date, picklist, checkbox, or email) before the corresponding data batch is loaded. Skipping this step results in data landing in wrong columns or being silently dropped if the destination field does not exist.

Gauss Box Deals, Leads, and Activities carry owner assignments tied to Gauss Box user accounts. We map owner email addresses to Twenty's user directory. Any Gauss Box owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before the record import resumes. Inactive Gauss Box user accounts that are still referenced in owner fields are flagged separately so the customer can decide whether to provision a corresponding inactive Twenty User or reassign the records.

Gauss Box's configurable pipeline stages are enumerated per account and mapped to Twenty's Opportunity stage values. Stage names, probabilities, and order of presentation migrate as configured. If the Gauss Box account uses multiple pipelines (an advanced configuration), we map each Gauss Box pipeline to a separate Opportunity pipeline view in Twenty, or document the multi-pipeline requirement for the customer's admin to configure as separate Twenty pipeline filters post-migration.