Migrate from OneSuite to HighLevel

OneSuite Client records map directly to GoHighLevel Contact. The Client's contact details (name, email, phone, address), company information (if a business client), social links, and revenue data migrate as standard Contact fields. We preserve any OneSuite custom fields by remapping from the flattened slug structure (e.g., clientTier on the record) to a GoHighLevel custom field created before import. Client-to-Project relationships are preserved by resolving the associated Project to its GoHighLevel Opportunity equivalent.

OneSuite Clients flagged as business entities map to GoHighLevel Company (also called Account in some GHL contexts). The Company holds the business name, domain, address, and industry. If the OneSuite Client has both individual contact data and company data, we split it: individual contact fields go to Contact and company fields go to Company, linked by the Contact-to-Company relationship in GoHighLevel.

OneSuite Lead records with stages, source attribution, and scoring map directly to GoHighLevel Lead. Pipeline stages from OneSuite map to GoHighLevel pipeline stages within the Lead's pipeline. The OneSuite lead score migrates to a GoHighLevel custom field (lead_score__c) that the customer creates before migration. Tags from OneSuite migrate to GoHighLevel tags on the Lead record.

OneSuite Leads that represent active engagements or closed-won deals split into a GoHighLevel Contact (the person) and an Opportunity (the deal). We identify the split trigger during scoping: either a OneSuite pipeline stage change to a closed-won equivalent or a manual flag on the Lead record. This prevents orphaned Opportunities in GoHighLevel and preserves the full deal history.

OneSuite Projects have no direct GoHighLevel equivalent. We map Projects to GoHighLevel Opportunities with the Project name as the Opportunity name, Project status mapped to Opportunity stage, and the associated OneSuite Client mapped to the GoHighLevel Contact (or Contact + Company). Project tasks and milestones do not have a native GoHighLevel equivalent; we flag them for rebuild as GoHighLevel Tasks with due dates or a project management tool as a post-migration step. This is the primary structural adaptation point in this migration pair.

OneSuite Invoices map partially to GoHighLevel. Invoice line items, tax rates, payment status, and currency do not have a direct GoHighLevel equivalent object. We map Invoice status (paid, unpaid, overdue) to Opportunity custom fields or tag values, and invoice amounts to Opportunity Amount. GoHighLevel Payments can record individual payments against an Opportunity but does not support the multi-line invoice format with tax calculation that OneSuite provides. Invoices with complex multi-currency or custom tax configurations are flagged for manual reconciliation post-migration.

OneSuite Documents (attached to Clients or Projects) migrate as GoHighLevel Contact custom fields holding the document name and URL reference. Binary file content does not migrate directly; we transfer document metadata (name, type, URL) and flag any Documents exceeding the OneSuite storage tier cap (30 GB Freelancer, 60 GB Growing Agency) before migration so the customer can address storage before or after cutover.

OneSuite Files attached to Projects, Tasks, or Invoices migrate as GoHighLevel Attachments linked to the equivalent Opportunity or Contact. File metadata and URLs transfer; binary content is flagged for the same storage-tier pre-scan process as Documents. Files exceeding plan storage caps are not imported until storage is resolved.

OneSuite custom fields are returned by the API flattened directly onto the entity with their original slug as the property key (e.g., clientTier, leadScore, projectStatus). We parse the API response, extract each slug-value pair, and create equivalent GoHighLevel custom fields on the target object before migration. If a GoHighLevel custom field with the same name does not exist, we flag it for creation during the schema preparation phase so no custom field values are dropped at import time.

OneSuite Members (team users assigned to Projects, Clients, and Invoices) map to GoHighLevel Users. We resolve Members by email match against the GoHighLevel destination account's user list. Any OneSuite Member without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission mappings require post-migration configuration in GoHighLevel's team settings.