Migrate from Moskit to HighLevel

Moskit Contact records with a linked Company map to a GoHighLevel Company first (with the organizational name as the Company Name), then the person becomes a Contact linked to that Company via the dnd1_company_name field. Contacts without a Company association become standalone GoHighLevel Contacts. We preserve the Moskit contact's email, phone, custom properties, and owner reference. Portuguese labels on custom properties are preserved as-is and flagged in the field label glossary.

Moskit Empresa records map to GoHighLevel Company objects. The Company record is created before Contact import so that the Company Lookup on Contact is satisfied at insert time. HubSpot-style domain-based dedupe is not enforced; we use Company Name as the dedupe key. Custom fields on the Company object migrate to GoHighLevel custom fields of equivalent type (text, number, date, picklist).

Moskit Deals map to GoHighLevel Opportunities inside a Pipeline. The dealstage and pipeline fields map to the GoHighLevel Pipeline name and stage. Monetary value (amount) transfers directly. We create the Pipeline in GoHighLevel before importing Deals so that the pipeline_id reference is valid at import time. Closed-Lost and Closed-Won custom reason fields from Moskit become GoHighLevel custom text fields on the Opportunity.

Moskit Activities (tasks, calls, meetings, notes) map to GoHighLevel Activity records. Each activity type maps to the equivalent GoHighLevel activity type constant. Timestamps (created_at, updated_at) and owner assignment transfer with ActivityDate preserved for timeline ordering. Activity descriptions migrate as body text. Call duration and disposition, if set in Moskit, map to custom fields on the GoHighLevel Activity.

Moskit Projects are deal-spawned and carry a reference to the originating Deal. We import Deals first, capture the new GoHighLevel Opportunity IDs in a lookup table keyed by Moskit Deal ID, then import Projects in a second pass injecting the resolved Opportunity IDs. Projects without a deal link are flagged during scoping: these may become GoHighLevel Tasks (with a custom project_name field) or Opportunities depending on the customer's preferred structure. Subtask-level detail migrates as separate Task records linked to the parent.

Moskit Users (name, email, role, active/inactive status) export via the API and map to GoHighLevel Users by email match. Active status transfers as-is; inactive users are imported with a deactivation flag and a custom field moskit_original_status__c to guide GoHighLevel admin setup. Users without an email in Moskit are flagged in the reconciliation report.

Moskit pipeline stages (names and order) become GoHighLevel Pipeline stages. Win probability percentages set on Moskit stages transfer as GoHighLevel stage probability values. Stage-level automation triggers (if any) are documented as part of the automation inventory and not migrated as code.

Moskit custom fields on Contacts, Companies, Deals, and Activities require per-object schema discovery since there is no bulk custom field enumeration endpoint. We run separate schema-discovery requests per object type before pulling record data. Field types (text, number, date, picklist, checkbox) map to GoHighLevel field types. Portuguese picklist values preserve their original strings in GoHighLevel.

Moskit WhatsApp sync stores conversation references linked to Contact records: timestamps of first and last message, participant count, and total message count. The actual message content is in WhatsApp's infrastructure, not Moskit. We import the conversation metadata as custom fields on the GoHighLevel Contact record and flag the message content gap explicitly in the scoping report. Customers who need full WhatsApp message history should export from WhatsApp Business directly before migration.