Migrate from Getfly CRM to HighLevel

Getfly Account records are the primary contact container and map directly to GoHighLevel Contact. Standard fields (name, phone, email, address) migrate as typed Contact fields. Custom fields on Getfly Accounts map to GoHighLevel Contact custom fields, which we pre-create in the destination account using GoHighLevel's Custom Fields settings before import. The mapping resolves the Getfly customer-specific subdomain context to a single GoHighLevel account namespace.

Getfly Account records also map to GoHighLevel Company when the source Account holds organizational data rather than individual contact data. We apply a name-pattern heuristic (Accounts containing legal entity suffixes such as 'Ltd', 'Inc', 'JSC', 'TNHH') are mapped to GoHighLevel Company alongside Contact. The customer's admin confirms the split logic during scoping. GoHighLevel Company enables Contact-to-Company linking for accounts with multiple contacts.

Getfly Products with pricing, SKU, and custom fields (stored as nested detail_custom_fields) map to GoHighLevel Products. We flatten custom fields into scalar product custom fields during the export transform. Product pricing and SKU migrate to GoHighLevel's product pricing fields. If the destination GoHighLevel account uses products within Opportunities, we configure the product catalog before Opportunity import begins.

Getfly pipeline stage names are customer-specific and extracted from the full stage configuration during discovery. Each Getfly stage maps to a GoHighLevel Pipeline Stage with the same name and order. Stage probabilities migrate from Getfly's custom probability settings to GoHighLevel's stage probability field. If Getfly has multiple pipelines, we create separate GoHighLevel Pipelines (one per source pipeline) and map each stage accordingly.

Getfly Deals map to GoHighLevel Opportunities. The Deal's linked stage maps to the corresponding GoHighLevel Pipeline Stage. Deal value (amount), close date, owner assignment, and linked Account (via Contact or Company lookup) migrate to GoHighLevel Opportunity fields. We resolve the GoHighLevel Contact or Company reference at migration time using email-based lookup tables.

Getfly Activity records (type, date, duration, owner) map to GoHighLevel Tasks for general activities and to GoHighLevel Appointments for meeting-type activities. We preserve the original timestamp as the activity date. Owner assignment migrates by resolving the Getfly user email to a GoHighLevel user account. GoHighLevel does not have a separate Event object; all time-blocked activities land as Appointments.

Getfly PABX call logs (direction, duration, recording URL) map to GoHighLevel Tasks with call disposition fields. Recording URLs are URL-referenced only in Getfly; we download the audio file during export and re-upload to GoHighLevel's native call recording storage. If the customer's PABX system is replaced alongside the CRM, recording continuity is explicitly scoped. GoHighLevel's calling is usage-based; the customer's account must have calling enabled before call records import.

Getfly Users mapped as record owners (name, email, role) export to a roster used for GoHighLevel User mapping. We resolve Getfly user email to GoHighLevel User by email match. Any Getfly owner without a matching GoHighLevel User goes to a reconciliation queue for the customer to provision before record import resumes. GoHighLevel's flat-user model means all active migrated users can be granted full access regardless of tier.

Getfly Marketing Campaigns (name, start/end dates, linked accounts) map to GoHighLevel Campaigns. Campaign membership (which Accounts were contacted) migrates as a tagged list on the GoHighLevel Campaign. GoHighLevel's Campaign object supports membership tracking and UTM attribution for pipeline reporting. Campaign-level activity history is not preserved as GoHighLevel engagement records unless those activities are already logged as Getfly Activities.