Migrate from Marketing Star to HighLevel

Marketing Star contact records map directly to GoHighLevel contact records. Every contact must have at least an email address or a mobile phone number; we validate this during the profiling phase and flag any record missing both fields before migration begins. Standard fields (first name, last name, email, phone, address) map directly. Custom contact properties from Marketing Star migrate to GoHighLevel custom contact fields, created in the destination account before import. SMS opt-in status migrates separately to GoHighLevel's SMS consent field.

SMS contact records in Marketing Star are distinguished by mobile phone number and carry their own opt-in status independent of email consent. We preserve mobile opt-in and opt-out timestamps as separate fields on the corresponding GoHighLevel contact record rather than merging them into a generic consent flag. This matters for compliance in jurisdictions with explicit SMS consent requirements.

Marketing Star list membership translates to GoHighLevel tags on the contact record. Each list the contact belongs to becomes a tag in the format 'List: [ListName]'. We export the full list membership matrix and apply tags during the contact import phase. If a contact belongs to multiple lists, it receives multiple tags. This approach replicates the audience segmentation logic without the hard per-list record cap that constrains Marketing Star tiers.

Marketing Star campaigns track multichannel sends (email, SMS, QR code triggers) but do not include deal or pipeline logic. We create a GoHighLevel pipeline named for each Marketing Star campaign and populate it with opportunity records representing the campaign's send history and aggregate metrics (send date, recipient count, open rate if available). High-level campaign performance metrics migrate as opportunity custom fields rather than native analytics, since GoHighLevel's reporting dashboards are separate from the opportunity record.

Marketing Star form structures and field definitions export as a field mapping document. We recreate each form as a GoHighLevel native form with equivalent field types. Form submission histories (lead capture records) migrate as contact records with the form source recorded in a custom field. If Marketing Star forms use conditional logic or field branching, we document that logic for manual recreation in GoHighLevel's form builder, which handles conditional fields natively.

Marketing Star landing pages are only available on the Ultimate tier ($500/month). We export page content, URL redirect configurations, and meta information. GoHighLevel's funnel and page builder is included on all tiers. We provide the exported content as HTML assets and redirect configurations so the customer's team can rebuild the pages in GoHighLevel's drag-and-drop builder. We do not migrate page templates or theme configurations as code.

Marketing Star automation workflows do not migrate to GoHighLevel as executable logic because the two platforms use incompatible workflow engines. We export each workflow's trigger, conditions, actions, and delays as a written inventory document. The document includes the workflow name, trigger type, all conditional branches, action sequences (email sends, SMS sends, field updates, list assignments), and recommended GoHighLevel workflow equivalents. The customer's admin rebuilds these in GoHighLevel's visual workflow builder post-migration.

Marketing Star QR codes tie to campaigns or forms and track physical-to-digital attribution. We export QR code metadata (code name, redirect URL, associated campaign) as contact custom fields on the records that were tagged by that QR code. GoHighLevel does not have a native QR code management object, so attribution is preserved as field data rather than a standalone object. The redirect URL configurations export as a reference document for the customer's team to update in any external QR generation tool.

Marketing Star user accounts map to GoHighLevel user records. We match by email address. Any Marketing Star owner referenced on a contact or campaign record without a matching GoHighLevel user goes to a reconciliation queue for the customer's admin to provision before the migration resumes. GoHighLevel's unlimited-user model means the provisioning step is straightforward and not constrained by a seat limit.