Migrate from WayMore to HighLevel

WayMore Contact records map to GoHighLevel Contact with standard fields (first name, last name, email, phone) preserved. Custom properties on WayMore Contacts map to GoHighLevel Contact custom fields created during schema setup. Opt-out and suppression status from WayMore maps to GoHighLevel's Contact DND settings to maintain SMS and email compliance. We extract via CSV from the WayMore dashboard contacts section.

WayMore Company records map to GoHighLevel Company with name, website, phone, address, and domain preserved. GoHighLevel links Companies to Contacts via a native association, so we resolve the Company reference on each Contact during import. The WayMore company domain field becomes the GoHighLevel Company website URL for dedupe matching.

WayMore Contact custom properties (text, number, dropdown, checkbox types) map to GoHighLevel Contact custom fields under Settings > Custom Fields. We document field names, types, and sample values during extraction and create matching fields in GoHighLevel before import. Picklist values in WayMore must be manually recreated as GoHighLevel dropdown options.

WayMore Company custom properties map to GoHighLevel Company custom fields using the same type-preservation process as Contact custom fields. GoHighLevel Company custom fields support text, number, date, dropdown, and phone types. Unique field constraints (up to 10 unique fields per Custom Object) apply only to Custom Objects, not Company records.

WayMore dynamic segments cannot be replicated as logic in GoHighLevel. We export the current membership of each segment as a static contact list, tagging each Contact with the segment name. In GoHighLevel, the customer's admin recreates SmartLists using GoHighLevel's filter builder with equivalent conditions. Active segment membership counts are preserved as tags for reference.

WayMore tags applied to Contacts export in the Contact CSV and import as Tags in GoHighLevel. Tags are associated with the correct Contact records during bulk import. Multiple tags per Contact are supported in both platforms. Tag-based filtering in GoHighLevel uses the Tags field on the Contact record.

WayMore email campaign metadata (name, subject, send date, send status) exports via CSV and maps to GoHighLevel Campaign records. Campaign content and templates are documented in the written inventory for the customer's admin to rebuild in GoHighLevel's campaign builder. Historical send statistics do not transfer; the customer reviews campaign performance in GoHighLevel from the cutover date forward.

WayMore SMS campaign records and message templates export via CSV. Opt-out status per Contact is preserved to maintain SMS compliance in GoHighLevel. Message templates require manual re-creation in GoHighLevel's SMS template editor. Active SMS automation triggers must be rebuilt in GoHighLevel's workflow builder.

WayMore automation workflow definitions (triggers, conditions, delays, actions) are documented as a structured written inventory with step-by-step descriptions, not migrated as executable code. GoHighLevel's visual workflow builder requires manual reconstruction. We note which workflows had high-volume active executions at cutover so the admin can plan re-entry sequences for affected contacts.

WayMore user accounts export as a list with name, email, and role. We map by email match against GoHighLevel users. Role-based access controls (admin, editor, viewer) must be manually reconfigured in GoHighLevel's team settings. Users without a matching GoHighLevel account go to a reconciliation queue for the admin to provision before contact import.