Migrate from Signpost to HighLevel

Signpost Contact records map directly to GoHighLevel Contact. Standard fields (name, phone, email, address) map 1:1. Contact owner assignment from Signpost maps to GoHighLevel User by email lookup. We flag any contacts with duplicate emails for the customer to resolve before import because GoHighLevel uses email as the primary dedupe key. Contacts without email addresses are imported with a placeholder email and flagged for customer review.

Signpost Business records (the top-level organizational entity) map to GoHighLevel Company. Business name becomes Company name; Business address becomes the primary Company address. If the customer operates multiple Signpost Business entities (common for agencies managing client businesses), each Business maps to its own GoHighLevel Company. The Signpost Business-to-Contact association migrates as a GoHighLevel Contact-Company lookup relationship.

Signpost Campaign records (SMS and email) migrate as GoHighLevel Campaigns with campaign name, type, and timing preserved. Campaign targeting criteria (which Signpost segments or tags were included) migrates as GoHighLevel Tags applied to the relevant Contacts. The automated trigger logic that drove when Mia sent campaign messages cannot migrate and is documented in the Mia automation inventory for manual rebuild as GoHighLevel Workflow triggers.

Signpost tracks review solicitation status (requested, responded, response sentiment, internal flag status) in its Review object. GoHighLevel does not have a native review object; we migrate the most recent review status and overall sentiment as custom Contact fields (review_request_status__c, last_review_response__c). Full solicitation history across all time is flattened into a notes field or custom text area. The customer rebuilds the automated review funnel in GoHighLevel using Workflows triggered by appointment completion or payment confirmation.

Signpost Appointments include scheduling data, customer association, staff association, and status. We map these to GoHighLevel Tasks with appointment type, duration, and status preserved in custom Task fields. If the customer uses Signpost's integrated calendar, appointment records map to GoHighLevel Calendar Events with the appointment time as Event start/end. Any custom appointment types (service categories, location fields) require GoHighLevel custom fields created before import.

Signpost Payments tracks payment status against invoices or estimates. We migrate payment records as custom objects or as line items attached to the relevant Contact or Opportunity depending on the customer's reporting needs. Note that Signpost Payments is a separate product tier; if the customer is not actively using it, this object may not be present in the export. We validate payment object presence during discovery and adjust the object mapping scope accordingly.

Signpost contact segments and tags migrate as GoHighLevel Tags applied to Contacts. We preserve the full tag list but flag any tags that originated from Mia behavioral scoring for the customer to audit. GoHighLevel Tags are simple string labels; complex segment logic that relied on Mia's scoring algorithm requires manual reconstruction as GoHighLevel Smart Lists using filter conditions.

Custom fields on Signpost Contacts and Businesses map to GoHighLevel Contact Custom Fields and Company Custom Fields respectively. Field types are preserved where possible: text to text, number to number, date to date. Multi-select picklist equivalents from Signpost map to GoHighLevel multi-select custom fields. Any field types without a GoHighLevel equivalent (such as Signpost-specific rating scales) are flagged for customer review during scoping.

Signpost User accounts and owner assignments on records map to GoHighLevel Users. We resolve owners by email address match. Any Signpost User without a matching GoHighLevel User account is held in a reconciliation queue; the customer provisions the GoHighLevel User account before record import resumes. Inactive Signpost users can be provisioned as inactive GoHighLevel Users to preserve owner attribution on historical records.