Migrate from Touchdown to monday CRM

Touchdown Contact records migrate to Monday.com CRM People entities attached to a CRM Board. We resolve the undocumented Contact field schema via authenticated API exploration during the discovery phase, then map each discovered field to a monday column type (text, number, date, dropdown, email, phone). Duplicate detection uses email as the dedupe key. Custom contact properties discovered during API exploration are mapped to custom monday columns or handled as text fields if the target column type is unavailable.

Touchdown Company records map to Monday.com CRM Entity records. The Company domain or website field populates the monday Entity's Website column. Entities are created before People import so that the People-to-Entity link is satisfied at the moment of Contact insert. If Touchdown Company schema includes custom fields, they map to monday Entity columns of equivalent type.

Touchdown Campaigns require reconstruction in Monday.com CRM because monday does not have a native campaign object. Each Touchdown Campaign becomes a monday Board, with Campaign status and audience size stored in board-level columns. Campaign audience segments are recreated as Group filters within the board, and segment membership is preserved as a tag or multi-select column on the relevant People records. We document the original segment membership for the customer's admin to finalize post-migration.

Touchdown Audience Segments have no direct monday.com equivalent, so we recreate them as filtered views on the relevant CRM Board. Each segment definition is documented during API exploration and translated into monday's filter conditions (by column, operator, and value). Segment membership is preserved as a tag column on People records so that the underlying data remains filterable in monday after migration.

Touchdown Email Templates contain personalized messaging content and merge fields that have no native template storage equivalent in Monday.com CRM. We export template body text and merge field names, store them as a structured document in monday's Docs or as a text column on a dedicated Board, and flag the merge field mapping for the customer's admin to reconfigure in any third-party email integration they adopt post-migration.

Touchdown engagement history (email opens, clicks, sends, calls, meetings, tasks) migrates to Monday.com CRM's Emails & Activities section on the relevant People or Entity record. We map each engagement type to the closest monday Activity type and preserve the original timestamp in the activity date column. Activity content and metadata are stored as notes or description fields in monday's activity log. If Touchdown engagement records include custom metadata, it is stored in custom columns or text fields.

Touchdown User and Owner records are mapped to Monday.com CRM workspace members by email. We resolve owner email addresses against the monday workspace member list during scoping. Any Owner without a matching monday user is placed in a reconciliation queue for the customer's admin to provision before record import proceeds. Owner assignment on records migrates as the monday Assignee field.

Touchdown custom field schema is not publicly documented, so we discover all custom field definitions during authenticated API exploration in the discovery phase. Each custom field is typed (text, number, date, checkbox, dropdown) and mapped to the closest Monday.com CRM column type. Fields with unsupported types (such as multi-checkbox or rich-text with embedded media) are stored as text with a note flagging the original data format for admin review.