Migrate from SwiftCRM to HighLevel

SwiftCRM Contacts store name, relationship type, Face ID-protected confidential data, and custom properties. We map these 1:1 to GoHighLevel Contact records via CSV export, preserving SwiftCRM's first name, last name, phone, email, and address fields. Custom properties unique to the SwiftCRM account are audited during scoping and mapped to GoHighLevel Contact custom fields created in Settings > Custom Fields > Contacts before import.

SwiftCRM Appointments carry a client link, scheduled time, reminder, and notification context. We map appointment records to GoHighLevel Opportunities (for deal-tracking use cases where the appointment represents a sales stage) or to GoHighLevel Calendar events (for scheduling and availability use cases). The mapping decision is made during scoping based on how SwiftCRM is being used; some records split across both destinations.

SwiftCRM stores client documents within the platform, praised in reviews for keeping client files structured. We export all E-Docs as files and map them to the corresponding GoHighLevel Contact record via attachment upload. File names and any associated document metadata are preserved as Activity Notes or Custom Fields on the Contact record where the destination supports attachment linking.

SwiftCRM Reminders are tied to specific clients or appointments with notification context. We map Reminder flags to GoHighLevel Tasks attached to the corresponding Contact record. The SwiftCRM reminder timestamp and body text become the Task due date and description respectively. Recurring reminder patterns are preserved as a custom field note for the customer's admin to rebuild as GoHighLevel Workflow triggers if needed.

Notification history tied to client interactions in SwiftCRM is migratable as Activity Notes or custom fields in GoHighLevel. We preserve the notification timestamp, type, and content as a GoHighLevel Activity Note linked to the Contact record. Notification volume and patterns inform the GoHighLevel Workflow rebuild scope documented for the customer's admin.

SwiftCRM tracks family and business relationship structures between contacts. We preserve these as Contact custom fields (for simple relationship types like spouse or business partner) or as a GoHighLevel Custom Object with Lookup relationships to Contact records (for complex hierarchies like multi-level family trees). The customer chooses the structure during scoping.

SwiftCRM beta-stage custom fields vary by account tier and account configuration. We audit available custom fields during scoping and map them to GoHighLevel equivalents. GoHighLevel distinguishes between Contact custom fields (attached to the individual) and Opportunity custom fields (attached to a specific deal); we audit the SwiftCRM field context and assign each to the correct GoHighLevel custom field type before creating the schema. Note: a field created as Contact type cannot be switched to Opportunity type after creation.

SwiftCRM user accounts and basic permissions are migratable to GoHighLevel Team Members. We map SwiftCRM users by email match to GoHighLevel Users. Any SwiftCRM user without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision before contact import resumes. GoHighLevel's role and permission model is configured separately in Settings > Team Management post-migration.