Migrate from Markate to HighLevel

Markate Customers map directly to GoHighLevel Contacts. The customer first name, last name, email, phone, address, and company name fields transfer as standard GoHighLevel Contact fields. The company name from Markate's merged customer-company record becomes the Contact's Company field or creates a separate GoHighLevel Company record if the customer has multiple contacts per business. We run duplicate detection on email during pre-flight to flag potential merges before import.

Markate stores company information within the Customer record. If a business in Markate has multiple Customer records representing different locations or contacts, we split these into separate GoHighLevel Contacts attached to a single Company record. The Company object in GoHighLevel holds the business-level address, phone, and website, while individual Contact records hold location-specific details.

Markate Work Orders hold job details, assigned team members, schedule, status, and line items. We map Work Orders to GoHighLevel Opportunities if the customer uses GoHighLevel's standard pipeline for job tracking. If the customer's Work Order schema is field-service-specific (service type, equipment, property address, technician assignment), we recommend a GoHighLevel Custom Object (Work Orders) with lookups to Contact and Company. The Work Order status field (scheduled, in-progress, completed, invoiced) maps to Opportunity Stage or a Custom Object status field.

Markate Estimates map to GoHighLevel Opportunities with the estimate status preserved (draft, sent, accepted, declined). The estimate total amount maps to the Opportunity Amount field. We hold Estimates as Opportunities until accepted; declined Estimates are imported as closed-lost Opportunities with a Loss Reason field. Accepted Estimates can be converted to Work Orders post-import.

Markate Invoices map to a GoHighLevel Custom Object named Invoice with fields for invoice number, date, due date, amount, balance due, and payment status. GoHighLevel does not have a native invoice object in the standard CRM; Invoice Custom Object is the standard pattern for migrating billing records. Line items from the Markate Invoice become Invoice Line Item child records linked to the parent Invoice.

Markate Items map to GoHighLevel Products. The item name becomes the product name, item SKU maps to the product code, unit price maps to the standard price, and item description maps to the product description. Items must be imported before Estimates and Work Orders that reference them so that the product reference is satisfied at import time.

Markate Categories define the catalog taxonomy for items and services. We map Categories to GoHighLevel Tags on the Product2 record if the customer's category structure is flat, or to a custom Product Category picklist field if the hierarchy matters. The customer chooses tag strategy during scoping.

Markate Expenses track job-related costs linked to Work Orders or Customers. We map Expenses to a GoHighLevel Custom Object named Expense with fields for vendor, amount, date, description, and the related Work Order or Contact as a lookup. Expense records are imported after Work Orders and Contacts to satisfy the lookup dependencies.

Markate Team Members are billable users assigned to Work Orders and Invoices. We map Team Members to GoHighLevel Users by email match. If a Markate Team Member has no matching GoHighLevel User, they are held in a reconciliation queue for the customer to provision before Work Order import begins. Active team member status from Markate maps to GoHighLevel User active flag.