Migrate from Combit CRM to HighLevel

Combit CRM Contacts migrate directly to GoHighLevel Contacts. Standard fields (first name, last name, email, phone) map to their GoHighLevel equivalents. We preserve the link to the parent Combit Address record by mapping the address data into GoHighLevel's address fields on the Contact. Any German-language picklist values (Anrede, Titel, Branch) are translated to English equivalents during the transform phase using a mapping table agreed upon during scoping. Custom fields defined on the Contact object are identified during discovery, typed (text, number, date, picklist), and pre-created as GoHighLevel custom fields before import.

Combit CRM's Address model stores contact locations as separate records linked to Contacts. We extract address fields (street, city, postal code, country) and map them into GoHighLevel's standard address fields on the Contact record. Multi-address scenarios (billing vs shipping) are resolved by identifying the address type flag in Combit and applying the appropriate GoHighLevel address slot. If both billing and shipping addresses exist on a single Combit Contact, we write both into GoHighLevel Contact using the standard and custom address fields.

Combit CRM Company records map to GoHighLevel Contacts with an organization association. GoHighLevel does not have a separate Account object equivalent to Salesforce or HubSpot; organization data (company name, website, industry, size) attaches to a Contact as organization fields. We extract the primary company fields from Combit Firmen records and write them into GoHighLevel Contact's business information fields. If the customer has a large company database with multiple contacts per organization, we document this during scoping and evaluate whether a Custom Object for Companies provides the needed relational structure.

Combit CRM Deals map to GoHighLevel Opportunities. The Deal's stage (Verkaufsphase) maps to a GoHighLevel pipeline stage. Deal value (Betrag) maps to the Opportunity amount field. Combit's configurable pipelines with custom stages translate to GoHighLevel's pipeline builder, where we recreate the stage sequence and probability percentages. Expected close date from Combit maps to GoHighLevel's close date field. The Deal owner maps to GoHighLevel's assigned user via email match.

Combit CRM's multiple configurable Deal pipelines require mapping to GoHighLevel's Opportunity pipeline structure. Each Combit pipeline becomes a GoHighLevel pipeline. Stage names in German are translated to English during the transform phase and recreated in GoHighLevel's pipeline builder with matching stage ordering. If a Combit pipeline uses custom stage colors or labels, we document these in the mapping spec for the customer's admin to reapply post-migration in GoHighLevel's visual pipeline editor.

Combit CRM Projects are multi-contact, multi-activity records that do not map to GoHighLevel's standard Opportunity object. We create a GoHighLevel Custom Object named Projects (API name: project_c) with custom fields matching the Combit schema: project name, description, start date, end date, budget, status, and assigned user. Projects link to the related Contact records via GoHighLevel's Custom Object association feature. Line items or deliverables within a Combit Project migrate as separate Custom Object records (Project Line Item) linked to the parent Project.

Combit CRM Activities include calls, meetings, tasks, and notes attached to contacts or projects. We map call activities to GoHighLevel Tasks with a call type flag; meetings to GoHighLevel Events with start/end times and location; tasks to GoHighLevel Tasks with status and due date; and notes to GoHighLevel Notes or as CRM notes. Activity date and description preserve. We flag the activity type (Anruftyp, Aktivitätstyp) to apply the correct GoHighLevel activity type. Historical timestamps are preserved by setting the GoHighLevel activity creation date to match the original Combit timestamp.

Combit CRM Users and owners map to GoHighLevel Users by email address match. We extract all distinct users referenced on Contacts, Deals, Projects, and Activities and resolve them against GoHighLevel user accounts. Any Combit user without a matching GoHighLevel account enters a reconciliation queue for the customer's admin to provision before the main import phase begins. Assignment history from Combit is preserved as a custom field on each record (original_owner__c) rather than by reassigning records in GoHighLevel, which avoids permission complications during migration.