Migrate from Combit CRM to Freshsales

Combit CRM stores addresses as separate Anschrift records that link to multiple Kontakte (Contacts). Freshsales has no separate address object; address fields live directly on the Contact record. We flatten this relationship by extracting each Anschrift linked to a Kontakt, then embedding the primary address fields (street, city, postal code, country) into the corresponding Freshsales Contact. Secondary addresses from Combit (billing, shipping) map to Freshsales' additional address fields on Contact. The Combit Anschrift-to-Kontakt foreign key relationship is preserved during extraction and resolved at transform time by matching the contact reference ID.

Combit Contacts map directly to Freshsales Contacts. We map standard fields (name, email, phone, job title) and inherit the flattened address fields from the linked Anschrift. Combit Contacts with no associated Account map as standalone Freshsales Contacts; the customer's admin decides post-migration which should be converted to Leads in Freshsales' separate Lead model. We preserve Combit contact owner assignment in Freshsales OwnerId via email lookup.

Combit Firmen (Companies) map to Freshsales Accounts. The Combit company name becomes the Account name, domain information maps to Website, and industry or type fields map to Freshsales' custom fields or standard Industry picklist where applicable. We create Accounts before Contact import so that the Account lookup relationship resolves at the moment of Contact insert.

Combit Deals map to Freshsales Deals with their pipeline stages, deal value, owner, and expected close date. We reconstruct the pipeline structure by creating Freshsales pipeline stages that mirror the Combit stages during pre-migration configuration. Closed-Lost and Closed-Won statuses from Combit map to Freshsales Deal status values. Deal-contact associations migrate as Freshsales Deal contacts.

Combit Projects do not map cleanly to a single Freshsales standard object because Freshsales lacks a native project record type. We evaluate project usage patterns during discovery: projects with line items and budgets map to Freshsales Deals with custom fields for project metadata; multi-contact projects map to a Freshsales Custom Object with lookups to the relevant Contacts and Accounts. The customer chooses the approach during scoping, and we document the chosen model with its schema in the migration scope.

Combit Activities (calls, meetings, tasks, notes) map to Freshsales Activities, which is a unified module handling all engagement types. Activity type, date, duration, and description migrate directly. The link between an activity and its parent Contact or Project resolves to Freshsales Activity with the Contact or Deal reference preserved. Combit's separate activity type taxonomy (Anruf, Besprechung, Aufgabe, Notiz) maps to Freshsales Activity type values during transform.

Combit User records map to Freshsales Users by email address. We extract all distinct Benutzer email addresses from Combit records and match them against the destination Freshsales User table. Any Combit User without a matching Freshsales User enters a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on Contacts, Deals, and Activities resolve to Freshsales OwnerId through this mapping.

Combit custom fields across all objects require translation from German labels to English API-safe field names during mapping. We extract the full custom field schema (field name, data type, picklist values) during discovery, map data types to equivalent Freshsales field types (text, number, date, picklist, multi-select), and pre-create fields in Freshsales before data import. Any Combit custom fields with no Freshsales equivalent are flagged during scoping for the customer to decide whether to map to an existing standard field or create a new custom field.

Combit stores file attachments on records. We extract attachments to a file store with original filenames preserved, then create Freshsales attachment links pointing to the stored files using Freshsales' file attachment API. The Combit attachment-to-record relationship is preserved by linking each file to the migrated parent record (Contact, Account, or Deal) by record ID. Binary file content migrates in full; linked URLs that point to external storage do not migrate.

Combit supports categorical tagging of records. We extract tag values as a flat list per record, then map them to Freshsales Tags using the Freshsales Tags API. Multi-value tags from Combit (a contact can have multiple Kategorie values) map to Freshsales multi-tag format. We consolidate tags with identical names during deduplication to prevent tag proliferation at the destination.