Migrate from Signpost to Zoho CRM

Signpost Contacts map directly to Zoho CRM Contacts with name, email, phone, address, and business association preserved. We map Signpost's contact-level custom properties to Zoho custom fields on the Contact module. Any contact records with missing email addresses are flagged for customer review before import to avoid Zoho validation errors on required fields.

Signpost's Business object (the organizational entity that owns customers) maps to Zoho CRM Account. Parent-child Business hierarchies in Signpost map to Account hierarchies in Zoho. The Business name becomes Account Name, and any Business-level custom properties (industry, location type, number of locations) map to Zoho custom Account fields.

Signpost Campaigns (email and SMS) map to Zoho CRM Campaigns with campaign name, type, status, and target audience preserved. Campaign content and timing rules migrate as Campaign fields and notes. The automated trigger logic managed by Mia does not migrate; we document the trigger conditions and recommended Zoho Workflow equivalents in the automation handoff form.

Signpost's review solicitation records (request date, status, response, and whether the response was positive or flagged for internal resolution) have no native equivalent in Zoho CRM. We migrate the most recent review status as a custom picklist field on Contact (e.g., review_status__c with values pending, positive, flagged, none). Full solicitation history across all time is flattened into a multi-line text custom field (review_history__c) as a notes-style record.

Signpost Appointments (scheduling data, customer association, status, and appointment type) map to Zoho CRM Task records for actionable to-do items and Event records for calendar-scheduled meetings. We preserve appointment type as a Task custom field and location as the Task or Event location field. Custom appointment types that Signpost defines are recreated as Zoho custom Task Status values during schema setup.

Signpost Payments (payment status against invoices or estimates) migrate as custom Zoho CRM records in a Payments custom module linked to the Contact or Account. If Zoho Inventory or Invoicing modules are active in the customer's Zoho suite, Payments map to the corresponding Invoice records. Signpost Payments requires a separate product tier; we flag this during scoping and confirm the customer's Zoho suite coverage.

Signpost custom fields on Contacts and Businesses map to Zoho CRM custom fields on the corresponding modules. We preserve field types where compatible (text, number, date, picklist). Fields with incompatible types (e.g., Signpost-specific formats not supported in Zoho) are flagged for customer review. Zoho's 300-field per-module limit applies; if the customer approaches this ceiling, we identify low-use fields for exclusion during scoping.

Signpost contact segments and tags used for campaign targeting migrate to Zoho CRM Tags on the Contact module. We preserve the tag name and apply it to the matching Contact records. Any segment logic that relied on Mia's behavioral scoring (e.g., automated re-tagging based on engagement) is flagged in the automation handoff form as requiring a Zoho Workflow rebuild.

Referral and loyalty program enrollment records migrate as custom Contact fields (enrollment_status__c, referral_code__c) or a linked custom module depending on the complexity of the program's data structure. Program rules (point accrual, reward tiers, expiration) do not migrate and require manual setup in Zoho.

Signpost User accounts and owner assignments on records map to Zoho CRM Users. We match by email address. Inactive Signpost users are created as inactive Zoho Users to preserve record ownership history. Any users without an email match go to a reconciliation queue for the customer to provision before record import proceeds.

Mia-driven automation rules are not accessible via any documented export endpoint. We do not migrate them as code. During scoping, we interview the customer on every active Mia rule (trigger conditions, action types, timing logic) and deliver a structured automation audit form mapping each rule to a Zoho Workflow or Blueprint equivalent. The customer's admin rebuilds the automation in Zoho post-migration.