Migrate from Visual Practice to HighLevel

Naive CSV export-import destroys relational data and truncates activity history

Visual Practice's native export produces flat CSV files that lose the relationship between contacts and companies, deals and contacts, and activity records and their parent objects. A naive import into HighLevel creates duplicate records, orphans company associations, and strips note and activity history. FlitStack AI uses API-level reads from Visual Practice to rebuild these relationships in HighLevel — contact-to-company links via HighLevel's companyId lookup, deal-to-contact associations via Opportunity contact roles, and activity parent links preserved as HighLevel task and event records with original timestamps and owner IDs intact.

Workflows and automations cannot be exported and must be rebuilt manually in HighLevel's Workflow Builder

Visual Practice stores workflow logic in a proprietary format that has no export path compatible with HighLevel's trigger-and-action model. HighLevel's Workflow Builder uses visual automation with conditions, time delays, webhooks, and CRM integration — entirely different from most basic practice management tools. FlitStack AI exports Visual Practice workflow definitions as screenshot-and-log reference documents so your HighLevel admin can manually rebuild each workflow in HighLevel's visual builder. Automations that trigger on specific field changes, date-based actions, or contact lifecycle events require HighLevel-native setup.

HighLevel's sub-account model requires pre-migration pipeline and custom field provisioning

If you use HighLevel sub-accounts to separate client data, each sub-account has its own pipeline configurations, custom fields, and user assignments. Migrating into a single sub-account and then splitting creates reconciliation complexity. FlitStack delivers a sub-account provisioning plan before data moves — specifying which pipelines, custom fields, and tags to create in each sub-account so records land in the correct isolation boundary on first import.

HighLevel usage-based costs for SMS, voice, and AI features represent a billing model shift

Visual Practice typically charges a flat monthly rate with no per-message or per-call costs. HighLevel's subscription covers the platform, but SMS messages, inbound voice calls, and AI-powered features (like AI agent interactions) are billed separately based on usage volume. FlitStack surfaces these costs in the migration plan and can flag any Visual Practice data that would trigger HighLevel usage-based billing (e.g., phone numbers stored as SMS-capable contacts) so your team sets appropriate expectations with HighLevel's billing team before go-live.

HighLevel API rate limits cap bulk migration throughput at 200,000 requests per day per sub-account

HighLevel's API allows 200,000 requests per day and 100 requests per 10-second burst per sub-account under standard plans. Large Visual Practice datasets (especially with extensive activity history) can exceed single-day migration windows. FlitStack throttles API calls to stay within HighLevel's rate limit buckets, retries 429 errors with exponential backoff, and splits large migrations across multiple days with delta-pickup to capture records modified during the window. Your team is notified if the migration extends beyond the initially scoped timeline due to rate-limit pacing.