Migrate from The Clinic Place to HighLevel

Clinical notes and appointments require custom object setup before migration can run

HighLevel has no native clinical documentation object — appointment history and clinical notes from The Clinic Place cannot be imported into standard Contact or Company fields. FlitStack AI creates the clinical_appointment and clinical_note Custom Objects in your HighLevel account before data lands, with relationship fields linking each record back to the Contact. This requires schema setup as a prerequisite step. If your account is on a plan that restricts custom object creation, this needs to be resolved with HighLevel before migration proceeds. We deliver a schema setup plan at project kickoff so your HighLevel admin can create the objects or grant FlitStack API access to create them.

Billing and insurance records have no functional equivalent in HighLevel

The Clinic Place tracks invoices, payments, insurance claims, and outstanding balances as operational data. HighLevel does not include accounts-receivable management, insurance verification, or claim tracking — these features do not exist in the platform. We migrate billing and insurance records as read-only custom objects (financial_record and insurance_info) on the Contact. This means billing status cannot trigger HighLevel automations or workflows natively. If you rely on The Clinic Place's billing workflow for payment follow-ups, you will need to rebuild those triggers in HighLevel using the financial_record status field as a data source for a workflow condition.

Appointment scheduling is CRM-linked in HighLevel, not clinical-queue-based

The Clinic Place includes appointment scheduling with digital queues, room assignments, and provider-specific slot management. HighLevel's Calendar feature handles appointment booking but is designed for sales and service appointments — it does not support clinical queue management, multi-room setups, or provider credentialing logic. Migrated appointment records land as historical records in the clinical_appointment custom object. Active scheduling must be reconfigured in HighLevel's Calendar module, and any appointment-reminder workflows must be rebuilt in HighLevel's Workflow builder using HighLevel's booking triggers rather than The Clinic Place's scheduling logic.

Intake forms and consent documents migrate as reference records only

The Clinic Place stores completed intake forms and signed consent documents as attachments or linked records. These migrate to HighLevel as intake_document custom objects with a document URL pointing to the file stored in HighLevel's file storage. The document itself re-uploads as a file attachment. However, HighLevel does not have a native intake-form builder that mirrors The Clinic Place's form logic. Completed forms cannot trigger HighLevel workflows unless you rebuild the form in HighLevel's native Forms module and re-link responses to existing Contact records.

HighLevel API rate limits cap bulk import throughput

HighLevel's API 2.0 enforces a limit of 200,000 API requests per day per sub-account and 100 requests per 10 seconds. For migrations involving more than 10,000 patient records plus appointment history and custom objects, this rate limit affects the bulk import window. FlitStack AI manages import pacing against this limit, batching records to stay within the 100-request-per-10-second ceiling. For large datasets, the migration clock time extends accordingly — we disclose expected throughput at scoping so there are no surprises on cutover day.