Migrate your Signpost data
AI-assisted CRM and marketing automation platform for local service businesses, built around an intelligent assistant named Mia that manages reviews, outreach, and customer communications.
In its favor
Why people choose Signpost
The signal that keeps Signpost on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Local service businesses choose Signpost for its AI assistant Mia, which automates review requests and customer outreach without requiring technical setup or marketing expertise.
The platform consolidates review management, SMS/email campaigns, appointment scheduling, and a shared inbox into a single tool that small teams can operate without a dedicated marketing staff.
Small businesses appreciate the automated review funnel—Mia catches unhappy customers before they go public, which reviewers describe as a significant reputational shield.
The per-business CRM model works well for single-location contractors and home-service companies that do not need the full feature set of enterprise CRMs.
Managed onboarding and agency support are cited by partners operating Signpost on behalf of multiple local clients, making it viable for franchise or home-service network setups.
Customers report that Signpost's pricing feels high relative to what they use, especially when the automated features require ongoing supervision to avoid over-messaging clients.
Slow loading times and syncing issues with large contact lists frustrate users as their business grows, with the platform not handling scale gracefully.
The Mia algorithm requires babysitting—users describe manually unsubscribing clients from review requests and adjusting automated follow-up timing to avoid appearing pushy.
Onboarding gaps lead to misunderstandings about how features work, with customers discovering limitations only after signing contracts, eroding trust in the sales process.
Customers cite billing discrepancies—being charged additional fees not mentioned during sales conversations—as a driver for churn and a reason not to return.
Reasons to switch
Why people leave Signpost
The recurring reasons buyers give for replacing Signpost. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Signpost fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Signpost pricing overview
Signpost uses a per-user pricing model. The entry tier starts around $15/month, with a widely reported Standard tier near $199/month. Enterprise pricing is custom and requires a sales conversation. No public free tier exists, and pricing transparency is consistently cited as a pain point in customer reviews.
Lite
Tier 1 of 4
$15/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Signpost's schedule — see our quote-based pricing →
What gets migrated
Signpost object support
Object-by-object support for Signpost migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts are the primary customer records in Signpost. Name, phone, email, business association, and address are standard fields. We map these 1:1 to the destination CRM's contact or person object.
Businesses
Mapping requiredSignpost is organized around businesses (often a client's own company or franchise location). We map Business records to the destination's Account/Company object, preserving the parent-child structure if multiple locations exist.
Campaigns
Mapping requiredSignpost campaigns span email and SMS with automated triggers managed by Mia. Campaign content, timing rules, and contact targeting are migrated; the automated trigger logic (Mia rules) requires manual recreation at the destination.
Review Requests
Mapping requiredReview solicitation records, including request timing, status, and customer response, are migrated as custom properties attached to the Contact since most destination CRMs do not have a native review object.
Appointments
Mapping requiredAppointment records include scheduling data, customer association, and status. We map these to the destination's calendar or task object and flag any custom appointment types for field-level mapping.
Payments
Mapping requiredSignpost Payments tracks payment status against invoices or estimates. We migrate payment records as line items or custom objects, noting that Signpost Payments is a separate product tier.
Automated Workflows
Not in this platformMia-driven workflow automations are behavioral rules that execute based on contact activity. These are not exported via API and must be manually documented and rebuilt at the destination. We provide a workflow audit document during scoping.
Custom Properties
Mapping requiredCustom fields on contacts and businesses are exported and mapped to destination custom fields. Field types are preserved where possible; incompatible types are flagged for customer review.
Shared Inbox Messages
Not in this platformMessage history from Signpost's shared inbox is not available via export. We migrate the contact record and note that message threads must be archived separately or considered lost.
Loyalty and Referral Programs
Mapping requiredReferral and loyalty program enrollment records are migrated as custom properties or linked objects depending on destination schema. Program rules require manual setup at the destination.
Tags and Segments
Mapping requiredContact segments and tags used for campaign targeting are migrated as tags or list memberships. We flag any segment logic that relied on Mia's behavioral scoring for manual reconstruction.
Users and Owners
Mapping requiredUser accounts and owner assignments on records are mapped to the destination user list. Inactive or permission-specific users may need to be created as placeholder accounts at the destination.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts are the primary customer records in Signpost. Name, phone, email, business association, and address are standard fields. We map these 1:1 to the destination CRM's contact or person object. |
| Businesses | Mapping required | Signpost is organized around businesses (often a client's own company or franchise location). We map Business records to the destination's Account/Company object, preserving the parent-child structure if multiple locations exist. |
| Campaigns | Mapping required | Signpost campaigns span email and SMS with automated triggers managed by Mia. Campaign content, timing rules, and contact targeting are migrated; the automated trigger logic (Mia rules) requires manual recreation at the destination. |
| Review Requests | Mapping required | Review solicitation records, including request timing, status, and customer response, are migrated as custom properties attached to the Contact since most destination CRMs do not have a native review object. |
| Appointments | Mapping required | Appointment records include scheduling data, customer association, and status. We map these to the destination's calendar or task object and flag any custom appointment types for field-level mapping. |
| Payments | Mapping required | Signpost Payments tracks payment status against invoices or estimates. We migrate payment records as line items or custom objects, noting that Signpost Payments is a separate product tier. |
| Automated Workflows | Not in this platform | Mia-driven workflow automations are behavioral rules that execute based on contact activity. These are not exported via API and must be manually documented and rebuilt at the destination. We provide a workflow audit document during scoping. |
| Custom Properties | Mapping required | Custom fields on contacts and businesses are exported and mapped to destination custom fields. Field types are preserved where possible; incompatible types are flagged for customer review. |
| Shared Inbox Messages | Not in this platform | Message history from Signpost's shared inbox is not available via export. We migrate the contact record and note that message threads must be archived separately or considered lost. |
| Loyalty and Referral Programs | Mapping required | Referral and loyalty program enrollment records are migrated as custom properties or linked objects depending on destination schema. Program rules require manual setup at the destination. |
| Tags and Segments | Mapping required | Contact segments and tags used for campaign targeting are migrated as tags or list memberships. We flag any segment logic that relied on Mia's behavioral scoring for manual reconstruction. |
| Users and Owners | Mapping required | User accounts and owner assignments on records are mapped to the destination user list. Inactive or permission-specific users may need to be created as placeholder accounts at the destination. |
Gotchas
What to watch for in Signpost migrations
Issues we've hit on past Signpost migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Mia workflow automations are not exportable
Shared inbox message history is not exported
Slow contact list performance indicates export risk
Review request history requires custom property reconstruction
Billing model and contract terms are opaque
| Severity | Issue |
|---|---|
| High | Mia workflow automations are not exportable |
| High | Shared inbox message history is not exported |
| Medium | Slow contact list performance indicates export risk |
| Medium | Review request history requires custom property reconstruction |
| Low | Billing model and contract terms are opaque |
Leaving Signpost?
Where Signpost customers move next
12 destinations Signpost can migrate to.
How a Signpost migration works
Four steps, Signpost-specific
Connect
Not publicly documented into Signpost. Scopes limited to read-only on the data we move.
Map
We translate Signpost-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Signpost quirks before production.
Migrate
Full migration with Signpost rate-limit handling. Rollback available throughout.
FAQ
Signpost migration FAQ
Answers to the questions buyers ask most during Signpost migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Signpost migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Signpost.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Signpost setup and destination — written quote back within a business day.