Migrate from Composity CRM to HighLevel

Composity's Account object maps to a GoHighLevel Company record and optionally to a Contact record depending on data model preference. We create the Company first, then create Contacts linked to it. The Account name becomes the Company name field, and address, industry, and status fields map to their GHL equivalents. Owner assignment resolves by email match to the GHL User.

Composity Contacts migrate directly to GHL Contacts with name, email, phone, and role preserved. The Account-Contact relationship maps to the GHL Contact's Company field. Custom contact fields from Composity's Custom Data module migrate to GHL Custom Fields on the Contact object. We preserve the original Composity contact ID in a custom field for reconciliation.

Composity Leads from the Campaign & Lead Management module migrate to GHL Contacts with lead status, source, and qualification data preserved in custom fields. GHL does not have a separate Lead object by default; unqualified prospects live as Contacts with a lead_status custom field. We set the contact type or tag to distinguish migrated Leads from migrated Contacts.

Composity Opportunities map to GHL Opportunities with deal name, value, expected close date, and stage preserved. Stage names migrate as GHL pipeline stage values, and probability weights transfer to the stage configuration. Owner assignments resolve by email match to GHL Users at migration time.

Composity pipeline stages (user-defined in CRM settings) are recreated in GoHighLevel with matching names, order, and probability percentages. Each stage maps to a GHL pipeline stage value, and the stage probability is set in the pipeline configuration.

Composity Invoices migrate to GHL as either activity records attached to Contacts (if treated as billing history) or as a custom Invoice object if the customer requires line-item detail. Partially paid invoices carry forward outstanding balance as a custom field. Full invoice PDF documents migrate as attachments to the related Contact or custom Invoice record.

Composity Products map to GoHighLevel Products with name, SKU, price, and description preserved. Product-to-quote and product-to-invoice associations migrate as Opportunity line items in GHL.

Composity's Projects module (Growth tier and above) has no native GoHighLevel equivalent. We design a GHL Custom Object named Project during scoping, mapping project name, status, dates, assigned resources, and custom project fields to typed custom object fields. The customer configures any project-specific workflows post-migration.

Composity's Production module with BOM (bill of materials) references has no GoHighLevel equivalent. We extract production records and map them to a GHL Custom Object named Production Order, preserving BOM references as custom fields. This requires explicit schema design during scoping and is not a standard field-to-field migration.

Composity Inventory items (SKU, quantity, warehouse location, reorder level) map to GHL Products or a custom Inventory object depending on whether the customer needs warehouse tracking. Quantity discrepancies and negative stock values present at migration time are flagged in a reconciliation report.

Composity documents export one file at a time with no bulk download. We build a file inventory during discovery, download files in parallel where possible, and reattach to the correct GHL Contact or Company record using filename or metadata matching. Upload date and original filename are preserved.

Composity Activities (calls, emails, meetings, notes) attached to Contacts migrate to GHL Activity records. Activity type, date, description, and the linked Contact record are preserved. Interaction data export depends on Composity's module activation state; we audit available activity history during discovery.

Composity custom fields from the Custom Data module are reverse-engineered at scoping time. We create equivalent GHL Custom Fields on the target object with matching data types (text, number, date, dropdown) and migrate values during the record import phase.

Composity Users map to GoHighLevel Users by email match. Owner assignments on Contacts, Accounts, and Deals resolve to the matched GHL User. Users without a matching GHL account go to a reconciliation queue for admin provisioning before migration proceeds.