Migrate from mQuest to HighLevel

Direct field-to-field map for all standard name, email, phone, and address properties. HighLevel Contact custom fields hold any mQuest contact properties that do not map to built-in fields.

HighLevel Companies store organization records independently of Contacts. mQuest company properties map to Company custom fields if they exceed HighLevel's built-in Company field set.

HighLevel Opportunities track deal records linked to Contacts. Each Opportunity attaches to a Contact (or multiple via Opportunity Contact Roles) and belongs to a specific Pipeline Stage.

mQuest pipelines map to HighLevel Pipelines. Each pipeline stage becomes a HighLevel Stage within that pipeline. Stage order and probability values require value-by-value mapping since pick-list values are arbitrary per pipeline.

mQuest tags translate directly to HighLevel tags. Tag taxonomy is preserved as-is — HighLevel applies tags to Contacts, Companies, and Opportunities without restriction. No tag limit applies.

HighLevel Notes attach to Contact, Company, or Opportunity records. Original timestamps and note authors are preserved in the note body metadata. Rich-text formatting converts to HighLevel's note format.

Call logs, meeting records, and completed tasks from mQuest migrate as HighLevel Tasks linked to the parent Contact. Task type (call, meeting, email) maps to HighLevel Task categories.

HighLevel distinguishes Contact custom fields from Opportunity custom fields. All mQuest contact-level custom properties that have no built-in HighLevel equivalent are created as Contact custom fields before migration.

Deal-specific properties from mQuest migrate to HighLevel Opportunity custom fields. These fields display only within the Opportunity record and support pipeline-specific automation triggers.

mQuest entities with custom schemas map to HighLevel Custom Objects. HighLevel's Custom Object API supports relationship definitions that link custom records to Contacts or Opportunities — critical for N:N associations.

mQuest owner IDs resolve to HighLevel users by email match. Unmatched owners are flagged before migration — either invited to HighLevel first or assigned to a fallback user to preserve record ownership continuity.

mQuest file attachments are downloaded and re-uploaded to HighLevel's file storage, linked to the parent Contact, Company, or Opportunity record. File size limits apply — files exceeding HighLevel's limit are flagged for manual handling.

mQuest automations do not transfer. FlitStack exports the workflow definition (trigger events, conditions, actions, sequence order) as a structured JSON document and a step-by-step rebuild guide for HighLevel's Workflow Builder.

mQuest forms and landing pages are platform-rendered and cannot migrate. FlitStack documents field names, conditional logic, and thank-you page configurations so they can be recreated using HighLevel's form and funnel builders.