Migrate from Signpost to HubSpot

Signpost contacts migrate directly to HubSpot contacts. All standard properties (firstname, lastname, email, phone, address fields) map to HubSpot's corresponding contact properties. Original create dates are preserved as a custom datetime field since HubSpot's Createdate reflects the migration timestamp. Review-consent flags from Signpost are preserved as HubSpot contact properties for compliance reference.

Signpost companies map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer to HubSpot's matching company properties. Industry pick-list values are mapped value-by-value; where Signpost uses a value not present in HubSpot's default list, a custom value is added before migration so no industry data is lost.

Signpost deals migrate to HubSpot deals. Deal name, amount, stage, pipeline, close date, owner, and priority transfer directly. Stage names are mapped value-by-value per Signpost pipeline to HubSpot pipeline stage. Original stage-entered timestamps are preserved as custom datetime fields on the HubSpot deal for reporting continuity.

Signpost call records migrate as HubSpot engagements with type 'call'. Original call timestamps, duration, outcome, and owner are preserved. Each call is associated to the matching HubSpot contact or company record via the original Signpost association. Call content or notes attach to the engagement timeline in HubSpot.

Signpost email records migrate as HubSpot engagements with type 'email'. Subject, body, timestamp, and owner transfer. Emails are linked to the corresponding HubSpot contact or company. Attachments on emails are downloaded and re-uploaded to HubSpot Files, linked to the engagement record.

Signpost meeting and appointment records migrate to HubSpot meetings. Start time, end time, title, location, and attendees are preserved. Meetings link to the HubSpot contact or company records. Original organizer and invitee information transfers as engagement metadata. Calendar invitations and attached files are downloaded from Signpost and re-uploaded to HubSpot Files, with links attached to the meeting record.

Signpost notes migrate as HubSpot notes. Note body, create date, and owner transfer. Rich-text formatting from Signpost is preserved. Each note is associated to the corresponding HubSpot contact, company, or deal record. Original note ID is stored for traceability. Internal tags or categories from Signpost are preserved as note metadata where HubSpot's model supports custom metadata fields.

Signpost review-request history (which contacts were asked for reviews, at what date, with what outcome) has no native HubSpot equivalent. We create a custom multi-select or long-text property on HubSpot contacts to store review-request timestamps and outcomes. This preserves the historical review-automation data but is read-only in HubSpot.

Signpost tracks email and SMS marketing consent per contact. These flags transfer to HubSpot's native email and SMS subscription properties. Where Signpost stores additional granular consent data, custom HubSpot contact properties are created to preserve the full consent history for compliance reporting.

Signpost automated follow-up sequences and review-request workflows are platform-specific and do not have a HubSpot equivalent. FlitStack exports your Signpost workflow definitions as a structured reference document so your HubSpot admin can rebuild them in HubSpot workflows. The automation logic (triggers, delays, conditions) is preserved in the export, but execution requires HubSpot-side recreation.

Signpost custom objects (if your plan includes them) map 1:1 to HubSpot custom objects (Enterprise tier). Custom object associations that use N:N relationships in Signpost need HubSpot junction objects when the relationship is many-to-many. We surface this in the migration plan so your HubSpot admin creates the junction schema before data lands.

Signpost user records resolve to HubSpot owners by email match. Unmatched users are flagged before migration so your team can either invite them to HubSpot or reassign their records to a fallback owner. No record lands without a resolved owner assignment.

Signpost shared inbox conversations do not map to a native HubSpot object. Inbox threads are exported as notes with a specific label so your team can review them manually in HubSpot. For teams needing full inbox continuity, HubSpot's Conversations inbox must be set up separately post-migration with historical thread imports handled as a manual archival step.