Migrate from Market Maker to HighLevel

Direct map. HighLevel Contact stores first name, last name, email, phone, address, and custom fields. Source contact IDs preserved in a custom field for traceability and delta-run deduplication. During migration, each contact's original creation timestamp is retained as a custom datetime field, and any secondary email addresses are stored in a dedicated custom field to preserve communication history.

Market Maker companies map to HighLevel businesses. Business stores company name, website, address, industry, employee count, and custom fields. Contacts link to businesses via the contact record's business association field. We also map any industry classification codes to HighLevel's picklist values, and preserve the original company ID in a custom field for future reference and cross-system reporting.

Market Maker deals map to HighLevel opportunities. Each deal's stage, amount, close date, and owner migrate to the corresponding opportunity. Pipeline stages map to HighLevel pipeline stages with probability and forecast category. If a deal includes custom fields, they are transferred as custom properties on the opportunity, and any associated notes become conversation records attached to the opportunity.

Market Maker pipelines become HighLevel pipelines. Each source pipeline creates a separate HighLevel pipeline with its own stage sequence. Stage names, probabilities, and order are mapped value-by-value during migration. We also preserve any pipeline-specific automation triggers as references in the migration documentation, so they can be re-implemented using HighLevel's workflow builder after the data is loaded.

Market Maker tags migrate as a custom multi-select text field on the contact record. Tags are stored as comma-separated values for filtering and segmentation within HighLevel workflows. If tags contain hierarchical groupings, we flatten them into a single string but retain the original hierarchy in a separate custom field so you can rebuild groupings in HighLevel's filter logic.

Market Maker notes and activities migrate as HighLevel conversation records attached to the contact. Timestamps, owners, and activity type (call, email, meeting) are preserved in the conversation metadata. Any attachments linked to an activity are downloaded and re-uploaded to HighLevel's file storage, then linked back to the conversation record to preserve the full context of the interaction.

Market Maker custom objects map 1:1 to HighLevel custom objects when available on the destination tier. Custom object relationships that are many-to-many require junction objects in HighLevel, which we surface in the migration plan. We also verify that the destination tier supports the specific custom object field types used in your source, such as date, number, or lookup fields, and document any needed field type conversions.

Market Maker users are resolved by email match to HighLevel users. Unmatched owners are flagged before migration; their records are assigned to a fallback owner or held pending invitation to HighLevel. If a user has no email in Market Maker, we create a placeholder entry in HighLevel with a generated email address and mark it for verification during the handoff call.

File attachments on contacts, companies, or deals are downloaded from the source and re-uploaded to HighLevel's file storage, then linked back to the original record. File size limits of the destination apply. We also verify that each file's MIME type is supported by HighLevel, and rename any files with special characters to ensure compatibility with the platform's storage service.

Form submissions and source attribution that exist as standalone objects in Market Maker are preserved as custom fields on the contact record in HighLevel for reference. Original submission metadata is retained. If the submission includes nested data such as multiple choice answers, we flatten each answer into a separate custom field and store the raw JSON in a text field for complete auditability.