Migrate from Touchdown to Freshsales

Touchdown Contact records map directly to Freshsales Contact. We discover the full property schema during pre-migration API exploration since Touchdown does not publish a public schema. Standard properties (first_name, last_name, email, phone, company) map to Freshsales standard fields. Custom contact properties discovered via API map to Freshsales custom fields, with type conversion applied (date strings to Freshsales date format, multi-select to text area, etc.). Email addresses serve as the dedupe key during import.

Touchdown Company records map to Freshsales Account. We discover the Company object schema via API exploration since Touchdown's documentation does not confirm explicit Company object support. Company name maps to Account Name, domain to Website, and any discovered custom properties to Account custom fields. Accounts are created before Contact import so that the AccountId lookup relationship is satisfied at Contact insert time.

Touchdown Campaign records do not have a direct Freshsales equivalent because Freshsales has no campaign object. We migrate campaign metadata (name, status, start/end dates, audience size) as custom fields on a representative Deal record per campaign, or as standalone custom records if the customer needs to preserve campaign history. Campaign audience membership maps to Deal Contact roles or to a custom multi-select field listing associated contact IDs.

Touchdown Segments are audience filters based on contact properties and behavioral signals. We export segment definitions (filter conditions and logic) as JSON metadata and recreate them in Freshsales as either custom multi-select picklist fields on Contact (for static segments) or as Saved Views with filter criteria matching the original segment logic. The customer chooses between static field migration and dynamic Saved View recreation during scoping.

Touchdown Email Templates contain merge fields and personalized content. We export template HTML and associated merge field tokens, then map them to Freshsales Email Templates. Merge field syntax differs between platforms; we transform Touchdown tokens to Freshsales template variable format during the export phase. Templates with complex dynamic content requiring Touchdown's campaign logic are flagged as candidates for Freshsales workflow-based rebuild.

Touchdown engagement history (opens, clicks, sends, and implied interactions) migrates to Freshsales Appointment records (for meeting/call events) and Task records (for action items). Email send history migrates as Task records with a custom activity_type field set to email_sent. We preserve timestamps using Freshsales ActivityDate on Task and StartDateTime on Appointment. The original engagement type (open, click, send) is stored in a custom field for reconciliation against the source.

Touchdown custom field schema is not publicly documented, so we discover all custom field definitions during the pre-migration API exploration phase. We create matching custom fields in Freshsales (under Admin Settings > Customization) with type mapping applied: text properties map to Text fields, date properties to Date fields, numeric properties to Number fields, and multi-option properties to either Picklist or Text Area depending on the source cardinality. Custom fields are provisioned before any Contact or Account import begins.

Touchdown Owner records map to Freshsales Users. We resolve owners by email match during the migration run. Any Touchdown Owner without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Contacts, Accounts, and Deals migrates by resolving the Owner email to Freshsales User ID at insert time.