Migrate from The Practice to HighLevel

The Practice contact records map 1:1 to HighLevel Contacts. All standard properties (name, email, phone, address) transfer directly. Notes attached to a contact in The Practice become Notes in HighLevel with a ContactId link. Tags transfer to the tag field.

The Practice stores the client company as a text property on the Contact. FlitStack first creates a Company record in HighLevel, then resolves the Contact's company property to the new Company.id and writes it as Contact.companyId. Unmatched company names create a Company record automatically.

The Practice deals map to HighLevel Opportunities. Pipeline name becomes the HighLevel Pipeline; deal stage maps to the corresponding stage within that pipeline. Deal amount, close date, owner, and custom properties transfer as Opportunity custom fields.

Each pipeline stage name in The Practice is mapped value-by-value to the matching HighLevel pipeline stage. Probability and forecast category are applied per HighLevel stage defaults unless custom values are specified. Stage-entry timestamps are preserved as Opportunity custom datetime fields.

The Practice tag strings are transferred as-is to the HighLevel Contact tag field. HighLevel supports multiple tags per contact; each source tag becomes a separate tag value. Tag-based segmentation from The Practice is recreated as HighLevel contact filters.

The Practice custom properties on contacts are read and recreated as Custom Fields in HighLevel. Field type is inferred from the source value format — date fields, number fields, pick-list fields, and text fields each map to the closest HighLevel custom field type.

Deal-level custom properties in The Practice (e.g., deal_priority, deal_type) are created as Opportunity custom fields in HighLevel. The pipeline and stage already capture the primary deal context, so these custom fields add supplementary structured data.

Notes written in The Practice (session notes, coaching summaries) are migrated as HighLevel Notes with the Contact linked via ContactId. Original create dates and author information are preserved in custom datetime and text fields on the Note.

The Practice owner email addresses are resolved against HighLevel users by email match. Unmatched owners are flagged before migration so the team can invite them to HighLevel or assign a fallback user. Owner is written as Opportunity.ownerId and Contact.ownerId.

Files attached to contacts or deals in The Practice are downloaded, re-uploaded to HighLevel, and linked back to the corresponding record. HighLevel's 25MB per file limit applies; files exceeding this are flagged for splitting before the migration run.

Scheduled appointments from The Practice are migrated as HighLevel Calendar Events linked to the contact record. Original start/end times, timezone (converted from Eastern to UTC), and assigned user are preserved.

The Practice custom objects (if present) map 1:1 to HighLevel custom objects. Relationships between custom objects are mapped using HighLevel's relationship field definitions. Any N:N associations require junction object setup in HighLevel.