Migrate from Profi to HighLevel

Profi client profiles map 1:1 to HighLevel contacts. Standard fields including email, phone, name, and address map directly. Custom fields on the client profile migrate as custom fields on the HighLevel contact object. Owner assignment resolves by matching the owner's email address against existing HighLevel users.

Profi sessions have no direct HighLevel equivalent — they map to HighLevel tasks. Session name becomes task subject, start/end times become task due date and completion date, session status maps to task status, and coach assignment maps to task assignee. Original session timestamps are preserved as custom datetime fields in HighLevel.

Single-tier coaching packages map to HighLevel opportunities with name, amount, and stage. Multi-tiered membership structures (bronze/silver/gold) map to a custom object with tier name, price, and status fields. The mapping decision is made per migration based on the Profi data structure.

Profi booking links and appointment scheduling features map to HighLevel calendars, preserving calendar name and availability settings during migration. Recurring booking patterns in Profi, such as weekly recurring sessions or bi-weekly availability windows, map to HighLevel's recurring availability rules. One-off session links that do not follow a recurring pattern become single HighLevel calendar events linked to the corresponding contact record.

Profi drip-feed courses and digital content assets have no direct HighLevel equivalent. They migrate as a custom object with course name, content type, and enrollment count, or as an opportunity if the course is sold. Note: HighLevel cannot yet display custom object data dynamically on funnels or websites — external hosting may be required for course content delivery.

Profi custom fields on client profiles map to custom fields on the HighLevel contact object. Field types are preserved: text to text, number to number, date to date, pick-list to drop-down. Pick-list values require value-by-value mapping where the options differ between platforms.

Session notes and coach annotations in Profi migrate as notes attached to the corresponding contact or task in HighLevel. The original note timestamps and author information are preserved. Rich-text formatting such as bold text, bullet points, and hyperlinks is retained where Profi supports these features.

Profi tags and cohort labels migrate as HighLevel tags with exact name preservation. Tag names are copied character-for-character to ensure no data loss during migration. Tags applied to multiple record types in Profi, such as tags on clients and sessions, are applied to the corresponding contact or task in HighLevel.

Profi users and coaches map to HighLevel users by email match. User role in Profi (admin, coach, assistant) maps to HighLevel role (admin, user). If the role cannot be determined, the user is created as a standard HighLevel user and flagged for role assignment.

Profi automations and follow-up sequences do not migrate. They are defined by execution logic, not stored data. FlitStack exports a documented export of your Profi automation definitions — triggers, conditions, and actions — for your HighLevel admin to reference when rebuilding in the workflow builder.

Profi email templates do not migrate because they are stored as application-specific templates rather than raw data. We export the template content including text body, HTML code, and design specifications so your team can recreate each template in HighLevel's email template builder. Dynamic field placeholders used in Profi need to be updated to HighLevel's merge field syntax.

Profi's drip-feed scheduling for course content is platform-specific. Content migrates but the drip schedule does not. Rebuilt as a custom workflow in HighLevel or as a schedule in an external course hosting tool if HighLevel's current funnel limitations for dynamic custom object data apply.