Migrate from Touchdown to Salesforce Sales Cloud

Touchdown Contacts map directly to Salesforce Contact. For contacts that represent marketing audience members without a sales relationship, we evaluate mapping to Salesforce Lead instead. The mapping decision is made during scoping based on whether the Touchdown Contact has associated Deals or Opportunity custom properties. Email, name, phone, custom properties, and any personalization tokens migrate to the corresponding Salesforce Contact fields. Touchdown does not publish a Contact API schema, so we discover the field names via authenticated API exploration before migration.

Touchdown Company records map to Salesforce Account. Company name, domain, address, and custom properties transfer directly. We use Company domain as the Account Website and as the dedupe key during import. Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert. Touchdown's Company schema is not explicitly documented, so we confirm all available Company fields during the pre-migration API exploration phase.

Touchdown Campaigns map to Salesforce Campaign. Campaign name, type, status, start date, and end date transfer to the corresponding Salesforce Campaign fields. Touchdown campaign audience members migrate to Salesforce Campaign Members with the original opt-in status preserved in Member Status. Campaign performance metrics (opens, clicks, sends) from Touchdown migrate to Salesforce Campaign custom fields or Activity records because Salesforce Campaign does not natively store engagement metrics from external marketing platforms.

Touchdown Segments are audience definitions built from filter conditions. These have no direct Salesforce equivalent. We export the segment definition (filter logic, criteria, and included Contact IDs) and recreate them in Salesforce as a Campaign with a Static List or as a Salesforce Campaign List. The segment criteria are documented in the migration deliverable so the customer's admin can rebuild dynamic equivalents in Salesforce Reports or Flow if needed. Segment logic migration is a configuration task, not an automated data move.

Touchdown personalized messaging tools store templates with merge fields. We export template content and associated merge field names during the API discovery phase. Templates migrate to Salesforce as Email Template (for Sales Cloud email) or as Salesforce Content (for document management). Merge field syntax differs between platforms; we transform Touchdown merge tokens to Salesforce merge field format during the export. Email template HTML structure is preserved but tested in the Salesforce sandbox because CSS rendering differences can affect email client compatibility.

Touchdown custom contact properties migrate to Salesforce custom fields on Contact (API name ending in __c). We discover custom field names, data types, and picklist values during API exploration before migration. Type mapping is required: Touchdown multi-select properties map to Salesforce multi-select picklist, date properties map to Date fields, and boolean properties map to Checkbox fields. Validation rules in Salesforce are applied after migration and may make previously accepted values in Touchdown invalid; we flag these during scoping.

Touchdown Company custom properties follow the same discovery and mapping process as Contact custom fields. We export Company custom field names and types via API, map them to Salesforce Account custom fields, and apply type transformations (multi-select, date, boolean) during the load phase. Company custom fields that do not exist in Salesforce are pre-created before the Account import begins.

Touchdown engagement tracking (opens, clicks, sends, and any logged call or meeting activities) migrates to Salesforce Activity records. Opens and clicks migrate as Task records with TaskSubtype = Email; call logs migrate as Task with TaskSubtype = Call; meeting logs migrate as Event. The WhoId on each Activity points to the resolved Contact or Lead; the WhatId points to the related Campaign or Account. Touchdown's engagement object schema is not published, so we discover available fields during API exploration and map what we find to the closest Salesforce Activity schema.

Touchdown users referenced on Contact, Company, Campaign, and Activity records map to Salesforce User by email match. We resolve each distinct user email against the destination Salesforce org's User table during migration. Any Touchdown user without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId on records is set at migration time once the User mapping is validated.

If Touchdown contains custom objects (unconfirmed in published documentation but discoverable via API), they migrate to Salesforce custom objects with equivalent API names and __c suffixes. We pre-create the destination schema in Salesforce before migration, including all custom fields, field types, lookup relationships, and validation rules. Any undocumented custom objects in Touchdown are identified during the API exploration phase and added to the migration scope if the customer confirms they are production data.

If Touchdown contains Deal or Opportunity records built via custom properties or related objects, they migrate to Salesforce Opportunity. Stage, Amount, CloseDate, and OwnerId transfer directly. Pipeline structure maps to Salesforce Record Types and Sales Processes if multiple deal stages exist. The Opportunity-Account relationship is resolved at migration time using the AccountId lookup.

Touchdown audience Lists (stored groups of Contacts for campaign targeting) migrate to Salesforce Campaign Lists as Static Lists. Each list maps to a Salesforce Campaign with the list members as Campaign Members. Dynamic lists in Touchdown do not have a Salesforce equivalent; we document the filter criteria for the customer's admin to rebuild as a Salesforce Report or a Flow-based segmentation.