Migrate from PlanPlus Online to HighLevel

Account status verification and CSV export assembly

We verify the PlanPlus Online account is in good billing standing to ensure data export is not blocked. We then guide the customer through the manual CSV export process for each object type (Contacts, Companies, Deals, Tasks, Calendar Events, Projects, Custom Fields) from the PlanPlus web interface. Because PlanPlus has no API, this step requires the customer's active participation; we provide a checklist and field mapping spreadsheet to ensure each export covers all required columns. Planner Edition accounts export as personal data only and are handled separately from Business Edition team data. We allow three weeks for this phase and schedule a weekly sync to review exported file counts.

GoHighLevel account provisioning and schema design

We provision the GoHighLevel account at the appropriate tier (Starter $97/month for single business, Unlimited $297/month for agencies needing sub-accounts) and configure the initial schema. This includes creating custom fields on Contact, Company, and Opportunity to receive Franklin Covey priority metadata and custom goal references. If Projects are in scope, we pre-create the Project Custom Object with its custom fields and relationships. We configure the Opportunity pipeline stages to match PlanPlus deal stages with probabilities set during schema setup. Domain ownership and email authentication (SPF, DKIM, DMARC) are configured for LC Email deliverability.

Owner and user reconciliation

We extract every distinct PlanPlus user referenced on Contacts, Companies, Deals, Tasks, and Calendar Events and match by email against the GoHighLevel User table. Any PlanPlus user without a matching GoHighLevel User goes to a reconciliation queue. The customer's admin provisions missing GoHighLevel Users (active or inactive depending on the original PlanPlus user's status) before record import begins. We also document which external calendar systems were connected in PlanPlus (Google, Microsoft 365) for reconnection in GoHighLevel after migration.

Test migration in GoHighLevel sandbox or staging sub-account

We run a full test migration into a GoHighLevel staging sub-account using production-like data volumes from the exported CSVs. The customer reconciles record counts (Contacts in, Companies in, Opportunities in, Tasks in, Appointments in), spot-checks 20-30 records against the PlanPlus source, and reviews custom field population. Any field mapping corrections, stage name adjustments, or schema changes happen in this phase before production migration begins. This step typically runs for one week.

Production migration in dependency order

We run production migration in record-dependency order: Companies (first, as they are referenced by Contacts), Contacts (with owner assignment resolved), Opportunities (with stage probabilities and close dates), Tasks (with owner assignment), Appointments (with time zone normalisation), Projects (Custom Object with milestones as custom fields), and Custom Fields (mapped to the relevant object). Each phase emits a row-count reconciliation report before the next phase begins. Franklin Covey priority and goal metadata are loaded as custom fields during the Contact and Company phases. PlanPlus sync connection configurations are documented for manual reconnection in GoHighLevel.

Cutover, validation, and automation handoff

We freeze PlanPlus Online writes during cutover and run a final delta migration of any records modified during the migration window. We then enable GoHighLevel as the system of record. We deliver the PlanPlus automation and sync-connection inventory document to the customer's admin team, with GoHighLevel workflow equivalents recommended for each. We support a one-week hypercare window for reconciliation issues. We do not rebuild automations, landing pages, or forms inside the migration scope; those are separate engagements or internal admin tasks.