Migrate from Signpost to Microsoft Dynamics 365 Sales

Signpost Contacts with no associated Business record or with an inferred intent signal (unsubscribed, new inquiry) map to D365 Sales Lead. Signpost Contacts with an established Business association and active service history map to D365 Sales Contact attached to an Account. We compute the split using Signpost's associated Business ID, contact creation date, and any Mia scoring flags, preserving the original Mia-assigned status in a custom Contact field mia_status__c for customer review post-migration.

Signpost Business records map directly to D365 Sales Account. The Business name becomes Account Name, business address maps to Address composite fields, and any parent Business relationship (franchise or multi-location hierarchy) maps to the D365 Account Parent Account lookup. A custom field sp_business_id__c carries the original Signpost Business ID for reconciliation.

Signpost Campaigns (SMS and email) map to D365 Sales Campaign. Campaign name, target audience (contact list), send date, and campaign type migrate as Campaign records. D365 Campaign Member status tracks which Contacts and Leads were targeted; campaign send history and open rates migrate as custom fields on the Campaign since D365 does not natively store engagement metrics. Mia's automated trigger logic does not migrate; we document it in the automation audit form.

Signpost's native review object has no direct D365 equivalent. We migrate the most recent review request status (requested, responded, positive, flagged) as a custom Contact field sp_review_status__c, and the most recent response date as sp_last_review_response__c. Full solicitation history across all time is flattened into a custom Dataverse table sp_review_history__c with fields for request date, response date, outcome, and Mia disposition if available. D365 Sales Enterprise licensing is required for custom Dataverse tables; we flag this at scoping if the customer's D365 tier is Base or Sales.

Signpost Appointments map to D365 Sales Appointment activity records. Scheduling date, customer association (Contact or Lead), appointment status, and location migrate as Appointment fields. Custom appointment types (service call, consultation, estimate visit) are preserved as a custom field sp_appointment_type__c. If the customer uses Signpost's appointment reminders, those timelines are documented for rebuild in D365 Sales Workflows or Power Automate.

Signpost custom fields on Contacts and Businesses migrate to D365 custom fields on Contact, Account, or Lead. We preserve field types where possible (text, number, date, picklist); incompatible types (e.g., Signpost-specific structured objects) are flagged for the customer to review and map manually. All custom fields are provisioned in the destination D365 environment before migration begins, using the sp_ prefix to indicate source system origin.

Signpost contact segments and tags used for campaign targeting map to D365 Marketing Lists (static or dynamic) and to Contact tags. Dynamic Marketing Lists are reconstructed as D365 Marketing List member queries if the customer licenses D365 Marketing. Static lists migrate as Campaign Member records. Mia behavioral scoring segments are documented for manual rebuild using D365 Contact Intelligence or Power Automate conditions.

Signpost Owner assignments on Contact, Business, Campaign, and Appointment records map to D365 User records by email match. Any Signpost Owner without a matching D365 User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Signpost owners are migrated as inactive D365 Users with the sp_owner_original_id__c field set for reference.

Signpost referral and loyalty enrollment records migrate as custom fields on Contact (referral_status__c, loyalty_tier__c) if the enrollment count is low. For businesses with active loyalty programs and significant enrollment history, we create a custom Dataverse table sp_loyalty_enrollment__c with lookups to Contact. Program rules and tier logic do not migrate and require manual rebuild in D365.