Migrate from Signpost to Pipedrive

Signpost Contact records map directly to Pipedrive People. Name, phone, email, address, and business association transfer as standard Person fields. We resolve the Contact-to-Business link to populate the Organization field on the Person record. Custom properties on the Contact (such as preferred contact method or internal account tier) map to Pipedrive custom fields of matching type. Any Contact record with a missing email address is flagged for manual review because Pipedrive uses email as its primary deduplication key during import.

Signpost Business records map to Pipedrive Organizations. Business name becomes the Organization name, business address maps to the Organization address fields, and any parent-child Business hierarchy flattens into a top-level Organization with child Organizations linked via a custom parent_org field. The Business-to-Contact association is resolved by linking each Person record to the Organization after both objects are imported.

Signpost email and SMS campaigns migrate as Campaign records in Pipedrive, with campaign content (subject, body, timing rules) preserved in a custom field or attached Note. The automated trigger logic managed by Mia—behavioral scoring, send-time optimization, suppression rules—does not migrate. We document every active campaign's targeting criteria, send schedule, and A/B test setup in a written Campaign Audit Form so the customer's Pipedrive admin can rebuild the logic using Pipedrive's Workflow Automation feature (Advanced tier) or a third-party email tool like Mailchimp or ActiveCampaign integrated via Zapier.

Signpost's review solicitation history (request timestamp, response status, positive or negative flag, internal resolution notes) has no native Pipedrive equivalent. We migrate the most recent review request status as a set of custom fields on the Person record: last_review_request_date, last_review_response_status, and last_review_sentiment. Full solicitation history across all time is flattened into a custom long-text field or Notes entry on the Person. Customers who rely heavily on review funnel analytics should plan to maintain that reporting in a separate tool post-migration.

Signpost Appointment records map to Pipedrive Activities with type set to Calendar (meeting) or Task (appointment reminder). Appointment date, time, duration, customer association (linked to Person), and status transfer directly. Any custom appointment types defined in Signpost (such as consultation, estimate, or follow-up) are preserved as custom Activity type labels. Pipedrive's calendar integration must be configured post-migration to connect with the customer's existing calendar provider (Google Calendar or Outlook).

Signpost Payments records (a separate product tier) migrate as custom fields on the Person record for summary payment status or as a linked custom object for full transaction history. We flag payment records that reference invoices or estimates as separate objects requiring mapping to Pipedrive's Products and Deals if the customer intends to track revenue in Pipedrive post-migration. Note that Signpost Payments is a separate subscription; the customer's contract with Signpost for payment processing may have independent termination implications.

Mia-driven workflow automations are not exportable via API. We cannot migrate them as code. During scoping, we interview the customer on every active Mia rule (review request triggers, follow-up timing, campaign suppression logic, negative feedback triage) and document each in a Workflow Audit Form with trigger event, conditions, actions, and estimated Pipedrive Workflow Automation equivalent. The customer's admin rebuilds these rules in Pipedrive's Automation feature post-migration. This is manual work that we scope and document but do not execute.

Signpost contact tags and segment memberships migrate as Pipedrive Person tags, which are a native tagging system for People records. Tags used for behavioral scoring or Mia's targeting logic are flagged in the audit form because Pipedrive tags do not have scoring logic—behavioral segmentation requires custom fields or a third-party segmentation tool. The customer chooses tag strategy during scoping based on whether the tags represent simple labels or behavioral scores.

Signpost user accounts and owner assignments on records map to Pipedrive User records. We resolve owners by email match against the Pipedrive destination account's user list. Any Signpost Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Signpost users are mapped to inactive Pipedrive users if the customer wants to preserve assignment history.

Signpost custom fields on Contacts and Businesses migrate to Pipedrive custom fields on Person and Organization respectively. Field types are preserved where Pipedrive supports equivalent types (text, number, date, dropdown). Incompatible field types (such as Signpost-specific structured data) are flagged for the customer to review and either map to a text field or drop. Custom fields must be created in Pipedrive before migration begins so that they are available in the field mapping step.

Referral and loyalty program enrollment records migrate as a custom object in Pipedrive if the customer is on Advanced tier or above. Program enrollment status, referral code, and reward tier transfer as fields on the custom object. Program rules (point accrual logic, reward thresholds) require manual rebuild in Pipedrive's automation feature or a third-party loyalty tool. We document the program structure in the audit form for the customer's admin to evaluate against Pipedrive's capabilities.