Migrate from Signpost to Nutshell

Signpost Contact records map directly to Nutshell Person. Name, phone, email, address, and owner association migrate as standard fields. We resolve owner email against Nutshell's user list and hold any unmatched owners in a reconciliation queue. Signpost contact-level suppression flags and do-not-contact preferences migrate as a custom Person field since Nutshell uses the standard HasOptedOutOfEmail pattern for opt-out tracking.

Signpost Business records map to Nutshell Account. The business name becomes Account Name, and any parent-child business structure in Signpost maps to Account Hierarchy in Nutshell. We use Account as the dedupe key during import so that contacts can be linked to their associated Account at insert time. Business-level custom properties migrate as Account custom fields.

Signpost campaigns spanning email and SMS migrate as Nutshell email campaigns with campaign content, subject lines, and recipient lists preserved. Campaign timing rules and contact targeting criteria migrate as the campaign record is configured. The automated Mia trigger logic that governed when campaigns fired does not migrate; we document every active Mia campaign rule in a structured rebuild form so the customer can manually configure equivalent Nutshell automation triggers post-migration.

Signpost's review solicitation object tracks when a customer was asked for a review, the request status, and whether the response was positive, negative, or flagged for internal resolution. Nutshell has no native review object. We migrate the most recent review request status and response as a custom Person field called Last Review Request Status. Full solicitation history across all time is too complex to flatten into a single field; we document this limitation in the migration scope and recommend the customer manually archive historical review data if it is business-critical.

Signpost appointment records including scheduling data, customer association, status, and appointment type map to Nutshell Task records. We set Task Type to Appointment or Meeting and preserve the original scheduling date, time, and duration. Custom appointment types in Signpost become custom Task fields in Nutshell. Any appointment notes or descriptions migrate as the Task description field.

Signpost custom fields on contacts and businesses export with their field types preserved. We map text fields to Nutshell text custom fields, date fields to Nutshell date fields, and numeric fields to Nutshell numeric fields. Nutshell supports custom fields for People, Companies, and Leads with a character limit of 225 for text fields. Any field types that exceed Nutshell's supported types are flagged for customer review and flattened to text where feasible.

Signpost contact segments and tags used for campaign targeting migrate as Nutshell Tags on the Person record. Tag logic that relied on Mia's behavioral scoring is flagged for manual reconstruction in Nutshell's segmentation tool. We preserve the tag names exactly so the customer can rebuild equivalent segments post-migration without renaming.

Signpost user accounts and owner assignments on records map to Nutshell Users. We match by email address as the dedupe key. Any Signpost user who does not have a matching Nutshell account goes to a reconciliation queue for the customer to provision before record import resumes. Inactive Signpost users can be created as inactive Nutshell Users to preserve historical owner attribution.

Referral and loyalty program enrollment records in Signpost migrate as custom Person fields or a custom Nutshell object depending on the enrollment data complexity. Program rules and point balances do not migrate as executable logic; they require manual configuration in Nutshell. We extract enrollment status, referral source, and loyalty tier as structured fields and deliver a program reconstruction guide as part of the migration handoff documentation.