Migrate from Signpost to Freshsales

Discovery and export feasibility assessment

We audit the Signpost account for contact volume, business count, active campaigns, appointment records, custom properties, tags and segments, and active Mia automation rules as reported by the customer. We assess export feasibility based on data volume and performance behavior. For accounts with more than 10,000 contacts or signs of loading degradation, we recommend cohort-based export segmentation. We also ask for the Signpost contract to identify any early-termination obligations. The discovery output is a written migration scope including record counts per object and a list of Mia automation rules requiring manual documentation.

Mia automation documentation and Freshsales schema design

We deliver a structured workflow audit form for the customer to document every active Mia rule: trigger conditions, target audiences, message sequences, and timing logic. Simultaneously, we design the Freshsales destination schema: custom fields mapped from Signpost custom properties, Deal record types for migrated campaigns, Tags pre-created to match Signpost segments, and custom fields for review status and appointment metadata. Schema is validated in a Freshsales trial or sandbox before production migration begins.

Data extraction and cleansing

We extract Signpost data using available export tools in batches, throttled to avoid mid-job failures on accounts showing performance issues. We cleanse the export: deduplication by email on contacts, resolution of Business-to-Account parent references, flattening of appointment records into tasks or events, and mapping of custom properties to Freshsales field types. We flag any incompatible field types for customer review. Contact suppression flags from Signpost's messaging logic are preserved in custom fields for Freshsales consent configuration post-migration.

Sandbox migration and reconciliation

We run a full migration into a Freshsales sandbox or trial environment using production-like data volume. The customer reconciles record counts (Contacts in, Accounts in, Deals in, Tasks/Events in), spot-checks 25-50 random records against the Signpost source, and reviews custom field mappings. Any incorrect field assignments, missing custom properties, or data type conflicts are corrected before production migration. This step also validates that Freshsales API rate limits by tier (Growth: 1,000/hr, Pro: 2,000/hr, Enterprise: 5,000/hr) are sufficient for the record volume.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from Signpost Businesses, with parent hierarchy resolved), Contacts (with AccountId lookup resolved and dedupe by email), Deals (with campaign metadata in custom fields), Tasks and Events (appointments mapped and timestamped), custom fields and tags populated, and finally custom property validation. Each phase emits a row-count reconciliation report before the next phase begins. We freeze Signpost writes during the cutover window and run a delta migration of any records modified during migration.

Cutover, validation, and automation rebuild handoff

We enable Freshsales as the system of record after the delta migration completes and the customer confirms record counts match expectations. We deliver the Mia automation inventory document to the customer's admin team with recommended Freshsales workflow equivalents for each rule. Shared inbox threads are noted as unrecoverable; we confirm the customer has archived critical threads separately. We support a one-week hypercare window for reconciliation issues. We do not rebuild Mia automations as Freshsales workflows inside the migration scope; that is a separate engagement for the customer's admin or a Freshsales implementation partner.