Migrate from ForceManager CRM to HighLevel

ForceManager Companies map to GoHighLevel Locations, which represent physical or organizational entities in the CRM. The ForceManager company name, type, rating, and responsible person fields map to Location name, type, and assigned user. We use the company domain or primary address as a deduplication key during import. GoHighLevel Locations support custom fields which we pre-create to match ForceManager's z_-prefixed Company extra fields before migration begins.

ForceManager Contact records map directly to GoHighLevel Contact records with owner assignments preserved. The Contact-to-Location relationship is resolved by matching the Contact's associated Company to the destination Location ID before insert. GoHighLevel Contact records support a phone, email, address, and custom field schema that we build out to match ForceManager's z_-prefixed Contact extra fields. Owner assignment migrates by resolving the ForceManager user email to a GoHighLevel user.

ForceManager Opportunities map to GoHighLevel Opportunities with stage, value, and responsible user preserved. The pipeline-to-stage mapping is built during scoping by mapping each ForceManager deal stage name to a GoHighLevel pipeline stage value. Custom opportunity fields from ForceManager's z_-prefixed schema migrate to GoHighLevel custom opportunity fields that we provision before import. Monetary values migrate as-is with any currency metadata preserved in a custom field.

ForceManager Sales Order and Sales Order Line entities have no native GoHighLevel equivalent. We handle this as a mapping rather than a direct object match by extracting Sales Order header data (order number, date, status, total value) into GoHighLevel Opportunity custom fields, and line item details (product, quantity, unit price) into a GoHighLevel custom Line Items configuration or into Opportunity custom fields as a structured text or JSON field. The customer reviews this mapping during scoping to confirm the preferred representation.

ForceManager Activities (logged calls, meetings, field interactions) map to GoHighLevel Tasks or Notes depending on the activity type. Call logs and meeting records with duration and disposition data map to Task records with the activity type preserved. Notes with rich text content map to GoHighLevel Notes linked to the parent Contact or Location. Activity dates and timestamps migrate as-is to preserve the chronological timeline. Owner assignments on Activities resolve to GoHighLevel users by email match.

ForceManager Calendar Events export separately from Activities and include event name, start and end datetime, location, and attendee associations. We map these to GoHighLevel Calendar Events with start and end time, title, and location preserved. GPS coordinates stored in ForceManager Event records are mapped to a custom field in GoHighLevel since the platform does not natively consume GPS data in calendar events.

ForceManager Tasks with status, due date, assignee, and description map directly to GoHighLevel Tasks. Completed status, priority, and owner assignment migrate as-is. Tasks without an assignee in ForceManager are flagged during scoping for manual assignment or default-owner assignment in GoHighLevel.

ForceManager User records map to GoHighLevel Users by email address as the deduplication key. Owner assignments on Companies, Contacts, and Opportunities reference User IDs in ForceManager, and we resolve these to GoHighLevel User IDs via email lookup before importing any records that carry owner references. Any ForceManager user without a matching GoHighLevel user is placed in a reconciliation queue for the customer to provision before migration resumes.