How long does a Touchdown to Microsoft Dynamics 365 Sales migration take?

Most migrations land between three and five weeks for accounts under 15,000 Contacts and 3,000 Campaign records with no custom objects and straightforward segment definitions. Migrations with large engagement histories (over 200,000 records), extensive email template libraries, complex custom field transformations, or multiple segment definitions requiring Dataverse view recreation move to six to ten weeks because of the API discovery phase and segment reconstruction scope.

Does Touchdown's API schema exist anywhere for us to review?

No. Touchdown does not publish a public API schema or documentation site. The data model is discovered per-customer through authenticated API exploration at the start of the migration. We enumerate the actual field names, types, and relationships in your specific Touchdown instance and share that discovery output as part of the migration scope document. Custom fields and any non-standard properties are captured during this phase.

What does a Touchdown to Dynamics 365 Sales migration typically cost?

Migrations under 15,000 Contacts, 3,000 Campaigns, and no custom objects land between $5,000 and $7,500. Migrations with large engagement histories, complex custom fields, or multiple segment definitions requiring Dataverse configuration move to $9,000-$14,000. Dynamics 365 Sales Professional licensing ($95/user/month) or Enterprise ($190/user/month) sits outside the migration fee. Touchdown's current cost ($49/user/month) is lower but does not include the pipeline, forecasting, and AI capabilities that drive the migration.

Do Touchdown Workflows and Sequences migrate to Dynamics 365?

No. Touchdown Workflows and Sequences are automation features that do not export as functional code to any destination platform. We do not migrate them. We deliver a written inventory of every active Workflow and Sequence with its trigger conditions, actions, and a recommended Dynamics 365 equivalent (Power Automate flows for workflow-style automation, or Sales Copilot sequences if the customer licenses that module). The customer's admin rebuilds them post-migration.

What happens to my Touchdown audience segments?

Segments are recreated as Dataverse Saved Views or Power Automate flows in Dynamics 365. We capture the filter logic during API discovery, document the segment definitions, and deliver them as configuration instructions rather than importable data. This is a design step rather than a direct migration because Dynamics 365 does not have a native segment object equivalent to Touchdown's audience segment feature.

Will my email templates and merge fields work in Dynamics 365?

We migrate email template content and map merge field tokens from Touchdown's format to Dynamics 365 token format. The template HTML and text content transfer as Email Template records. Merge field placeholders are mapped to Dynamics 365 field tokens based on the source field names discovered during API exploration. Any Touchdown-specific token syntax that does not have a Dynamics 365 equivalent is documented for manual review.

Can we keep Touchdown for marketing while moving sales to Dynamics 365?

This pairing is less common because Touchdown is itself a marketing-focused platform. If your organization needs to keep a marketing automation layer, Microsoft Dynamics 365 Customer Insights - Journeys (the rebranded Dynamics 365 Marketing) provides the closest equivalent within the Microsoft ecosystem and shares Dataverse as the underlying data platform with Dynamics 365 Sales. We handle marketing automation migrations separately from the CRM migration scope.

What engagement history migrates from Touchdown?

We migrate engagement records (calls, emails, meetings, tasks) that we discover during API exploration as Task, Email, or custom activity records in Dynamics 365. The exact structure depends on what Touchdown's API exposes per customer instance. Activity timestamps are preserved as ActivityDate to maintain the timeline ordering. Engagement metrics such as open counts or click counts migrate as custom fields on the activity record or as related CampaignInteraction records where the Dynamics 365 data model supports it.

Touchdown to Microsoft Dynamics 365 Sales Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Moving from Touchdown to Microsoft Dynamics 365 Sales is a platform category shift: Touchdown is a B2B marketing automation CRM positioned at the entry level, while Dynamics 365 Sales is an enterprise sales CRM with deep pipeline management, forecasting, and Microsoft ecosystem integration. Touchdown does not publish a public API schema, so we begin every migration with authenticated API exploration to discover the live data model before any field mapping begins. We map Contact records to Dynamics 365 Leads or Contacts based on qualification status, Companies to Accounts, and Campaigns to the Dynamics 365 Campaign object. Audience segments from Touchdown do not transfer as a data object; we export the segment definitions and recreate them as Dataverse views or filtered queries in the destination. Email templates migrate as content with merge field placeholders mapped to Dynamics 365 template tokens. Touchdown Workflows, Sequences, and Forms do not migrate as code; we deliver a written inventory of every active automation for your admin to rebuild in Dynamics 365.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Touchdown

What's pushing teams away

No publicly documented public API — integrations live inside the Microsoft ecosystem only, so customers needing external system connections (e-commerce, webinar tools, attribution) hit a ceiling.
Feature depth is modest compared with enterprise marketing platforms — multi-touch attribution, advanced scoring, and account-based marketing are limited relative to HubSpot, Marketo, or Salesforce Marketing Cloud.
Reliance on Microsoft Dynamics / Power Platform means customers leaving that stack effectively must leave Touchdown too; the product has no standalone CRM mode.
Limited public review footprint (small Gartner / G2 sample) makes vendor due diligence harder for buyers who rely on third-party validation.
Pricing details beyond the entry tier are not transparently published; buyers must contact sales for larger seat counts and SMS volumes.

Choosing

Microsoft Dynamics 365 Sales

What's pulling them in

Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How Touchdown objects map to Microsoft Dynamics 365 Sales

Each row shows how a Touchdown object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Touchdown

Contact

maps to

Microsoft Dynamics 365 Sales

Lead or Contact

1:many

Fully supported

Touchdown Contact records map to either Salesforce Lead (for unqualified prospects) or Contact (for qualified buyers tied to an Account). We evaluate Touchdown's lifecycle or engagement score properties during scoping to determine the split rule, since Touchdown does not enforce a Lead/Contact model. We preserve the original Touchdown contact ID and any scoring properties in custom fields on both Lead and Contact for audit and reconciliation.

Touchdown

Company

maps to

Microsoft Dynamics 365 Sales

Account

1:1

Fully supported

Touchdown Company records map 1:1 to Dynamics 365 Sales Account. We use the Company domain or name as the Account deduplication key during import. Account is provisioned before Contact import so that the AccountId lookup relationship is satisfied at Contact insert time.

Touchdown

Campaign

maps to

Microsoft Dynamics 365 Sales

Campaign

1:1

Fully supported

Touchdown Campaigns map to Dynamics 365 Campaign. Campaign name, type, status, and dates migrate as standard Campaign fields. Audience assignments from Touchdown migrate as CampaignMember records linked to the corresponding Account or Contact. Campaign financial values map to BudgetedCost and ActualCost fields on the Dynamics 365 Campaign.

Touchdown

Segment

maps to

Microsoft Dynamics 365 Sales

Dataverse View or Query

lossy

Fully supported

Touchdown audience segments do not have a direct Dynamics 365 equivalent as a data object. We export segment definitions during API discovery, capture the filter logic (field conditions, operators, date ranges), and recreate them as Dataverse Saved Views or Power Automate flows in the destination. The customer chooses the implementation approach during scoping.

Touchdown

Email Template

maps to

Microsoft Dynamics 365 Sales

Email Template

1:1

Fully supported

Touchdown email templates migrate as Dynamics 365 Email Template records. We export template content including HTML structure and merge field tokens, then map Touchdown tokens to Dynamics 365 token format (such as $fieldname or {fieldname}) based on the source field names discovered during API exploration. Template type (text, HTML, or both) is preserved.

Touchdown

Custom Field

maps to

Microsoft Dynamics 365 Sales

Custom Field

1:1

Fully supported

Touchdown custom field schema is not publicly documented, so we discover custom field definitions during the pre-migration API exploration phase. Each custom field is evaluated for Dynamics 365 data type mapping: text fields map to Text or Memo, number fields to Integer or Decimal, date fields to DateTime, and checkbox fields to Two Option. We pre-create the destination schema in a Sandbox before production migration.

Touchdown

Engagement Activity

maps to

Microsoft Dynamics 365 Sales

Activity (Task, Email, Note)

1:1

Fully supported

Touchdown engagement records (opens, clicks, sends, form submissions) map to a combination of Task records and custom activity fields in Dynamics 365. We do not have a documented engagement object schema from Touchdown, so API discovery determines the actual field structure per customer instance before we design the activity mapping.

Touchdown

User/Owner

maps to

Microsoft Dynamics 365 Sales

User

1:1

Fully supported

Touchdown Owner records map to Dynamics 365 User by email match. We extract all distinct owner references on Contact, Company, Campaign, and Engagement records, match against the destination User table, and flag any unresolvable owners in a reconciliation queue for the customer's admin to provision before record import proceeds.

Touchdown	Microsoft Dynamics 365 Sales	Compatibility
Contact	Lead or Contact1:many	Fully supported
Company	Account1:1	Fully supported
Campaign	Campaign1:1	Fully supported
Segment	Dataverse View or Querylossy	Fully supported
Email Template	Email Template1:1	Fully supported
Custom Field	Custom Field1:1	Fully supported
Engagement Activity	Activity (Task, Email, Note)1:1	Fully supported
User/Owner	User1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Touchdown gotchas

Low

Catalog website appears mismatched

Medium

Touchdown stores its data inside the Dynamics 365 / Dataverse tenant

Medium

SMS data and consent records require careful handling

Low

Templates and landing pages reference Microsoft-hosted assets

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Touchdown gotchas		Microsoft Dynamics 365 Sales gotchas
Severity	Issue	Severity	Issue
Low	Catalog website appears mismatched	High	Professional tier 15-table custom table limit blocks migrations
Medium	Touchdown stores its data inside the Dynamics 365 / Dataverse tenant	High	October 2024 pricing increase applies at renewal for all customers
Medium	SMS data and consent records require careful handling	Medium	Custom fields must be created in the UI before API writes
Low	Templates and landing pages reference Microsoft-hosted assets	Medium	Power Platform request limits apply to bulk migrations
		Medium	Activity records orphaned to inactive owners fail silently

Pair-specific challenges

Touchdown has no published API schema

Touchdown does not publish a public API schema or Swagger documentation. We begin every migration with authenticated API exploration to discover the actual field names, data types, and object relationships in the customer's specific Touchdown instance. This discovery phase adds scope to the migration timeline and must complete before field mapping is finalized. Custom fields and non-standard properties are discovered during this phase, not defined in advance.
Segment definitions require manual reconstruction

Touchdown audience segments are defined by filter logic that does not export as a data object. We capture segment definitions during API exploration, document the filter conditions and field references, and recreate them as Dataverse Saved Views or Power Automate flows in Dynamics 365. Segments cannot be imported as a standard object; they require a configuration step that we deliver as part of the migration package.
Engagement history structure is undocumented

Touchdown engagement tracking (email opens, clicks, form submissions, call logs) is implied by the product's feature set but the engagement object schema is not published. We discover engagement fields during API exploration and map them to Dynamics 365 activity records on a per-customer basis. Activity migration cannot begin until schema discovery is complete for the engagement objects.
Workflows and Sequences do not migrate

Touchdown Workflows (automation rules) and Sequences (engagement cadences) are not migrated as functional code. We do not have access to the automation execution engine or cadence logic for recreation. We deliver a written inventory of every active Workflow and Sequence with its trigger conditions, actions, and recommended Dynamics 365 equivalent (Power Automate flows or Sales Engagement sequences if the customer licenses Sales Copilot). The customer's admin rebuilds them post-migration.
Option set field values must be explicitly mapped

Dynamics 365 enforces strict type matching for option set fields: source and destination integer values must align or records are rejected during import. We verify option set value mappings during pre-migration validation and recommend using shared global option sets in Dynamics 365 where both source and destination values are controlled. If Touchdown option set integers do not align with Dynamics 365, we document the discrepancy for manual resolution or transform the values during import.

Migration approach

Six steps for a successful Touchdown to Microsoft Dynamics 365 Sales data migration

Authenticated API discovery

We begin with authenticated API exploration of the Touchdown instance using the customer's credentials. We enumerate all accessible endpoints, field names, data types, custom properties, and relationship references. The discovery output is a written data model map that defines the source schema before any field mapping is designed. This phase is unique to Touchdown because no public schema exists and the data model varies per customer instance.
Scope definition and segment inventory

We define the migration scope based on the discovered data model. We enumerate Contacts, Companies, Campaigns, Segments, Email Templates, Custom Fields, and Engagement records. We capture segment filter definitions for documentation and recreate planning. We also inventory active Touchdown Workflows and Sequences for the written handoff document. The customer reviews and approves the scope before schema design begins.
Destination schema design in Sandbox

We create the Dynamics 365 destination schema in a Sandbox environment: Account and Contact objects, Lead object if the split applies, Campaign object, Email Template structure, and any custom fields discovered during API exploration. We configure field types, option sets, and lookup relationships. The schema is validated in Sandbox before production migration begins.
Owner and user reconciliation

We extract all distinct Touchdown Owner references and match by email against the destination Dynamics 365 User table. Any Owner without a matching User goes to a reconciliation queue for the customer's admin to provision. Migration cannot proceed with records that reference unresolved OwnerIds. We validate the queue resolution before record import starts.
Production migration in dependency order

We run production migration in record-dependency order: Accounts (from Touchdown Companies), Contacts (with AccountId resolved and Lead-Contact split applied), Campaigns (with CampaignMember audience assignments), Email Templates (with token mapping), then Engagement history (Task and Email records with ActivityDate preserved). Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation handoff

We freeze Touchdown writes during cutover, run a final delta migration of records modified during the migration window, then mark Dynamics 365 Sales as the system of record. We deliver the Workflow and Sequence inventory document to the customer's admin team with recommended Dynamics 365 equivalents. We support a one-week hypercare window for reconciliation issues. We do not rebuild Touchdown Workflows or Sequences as Power Automate flows inside the migration scope; that is a separate engagement.

Platform deep dives

Context on both ends of the pair

Touchdown

Source

Strengths

Lives natively inside Dynamics 365, Power Apps, and Business Central — no third-party sync layer to break.
Multi-channel marketing in one suite: email, SMS, landing pages, forms, events, sales automation.
European hosting and GDPR-by-design positioning eases EU procurement.
Drag-and-drop template builder lowers the cost of running a small marketing team.
Entry-level pricing accessible to SMBs migrating off Mailchimp or basic email tools.

Weaknesses

No documented public REST API limits non-Microsoft integrations and migration tooling.
Feature depth lags enterprise platforms like Marketo, HubSpot Marketing Hub, and Salesforce Marketing Cloud.
Tightly coupled to the Microsoft Dynamics ecosystem; standalone use is not a supported deployment.
Small public review footprint makes buyer due diligence harder.
Pricing beyond the entry tier is not transparently published.

Microsoft Dynamics 365 Sales

Destination

Strengths

Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
Implementation typically requires costly certified partners, adding 30–50% to total project cost
Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

	Touchdown Source	Microsoft Dynamics 365 Sales Destination
Strengths	Lives natively inside Dynamics 365, Power Apps, and Business Central — no third-party sync layer to break. Multi-channel marketing in one suite: email, SMS, landing pages, forms, events, sales automation. European hosting and GDPR-by-design positioning eases EU procurement. Drag-and-drop template builder lowers the cost of running a small marketing team. Entry-level pricing accessible to SMBs migrating off Mailchimp or basic email tools.	Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises
Weaknesses	No documented public REST API limits non-Microsoft integrations and migration tooling. Feature depth lags enterprise platforms like Marketo, HubSpot Marketing Hub, and Salesforce Marketing Cloud. Tightly coupled to the Microsoft Dynamics ecosystem; standalone use is not a supported deployment. Small public review footprint makes buyer due diligence harder. Pricing beyond the entry tier is not transparently published.	Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal Implementation typically requires costly certified partners, adding 30–50% to total project cost Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Touchdown and Microsoft Dynamics 365 Sales .

Object compatibility
B
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
C
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
B
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
B
Touchdown: Governed by Dataverse Web API service protection limits (per-user/per-app rate ceilings published by Microsoft). Touchdown does not impose additional documented limits on top..
Data volume sensitivity
B
Touchdown doesn't expose a bulk API — REST + parallelization used for high-volume runs.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Touchdown to Microsoft Dynamics 365 Sales

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Touchdown

Microsoft Dynamics 365 Sales

How Touchdown objects map to Microsoft Dynamics 365 Sales

What specifically takes care here

Six steps for a successful Touchdown to Microsoft Dynamics 365 Sales data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Touchdown to Microsoft Dynamics 365 Sales migration cost

What are you migrating?

Frequently asked questions about Touchdown to Microsoft Dynamics 365 Sales data migrations

Can't find your answer?

Related migrations to explore

Move from Touchdown.
Land in Microsoft Dynamics 365 Sales , intact.

Migrate from Touchdown to Microsoft Dynamics 365 Sales

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Touchdown

Microsoft Dynamics 365 Sales

How Touchdown objects map to Microsoft Dynamics 365 Sales

What specifically takes care here

Six steps for a successful Touchdown to Microsoft Dynamics 365 Sales data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Touchdown to Microsoft Dynamics 365 Sales migration cost

Frequently asked questions about Touchdown to Microsoft Dynamics 365 Sales data migrations

Can't find your answer?

How long does a Touchdown to Microsoft Dynamics 365 Sales migration take?

Does Touchdown's API schema exist anywhere for us to review?

What does a Touchdown to Dynamics 365 Sales migration typically cost?

Do Touchdown Workflows and Sequences migrate to Dynamics 365?

What happens to my Touchdown audience segments?

Will my email templates and merge fields work in Dynamics 365?

Can we keep Touchdown for marketing while moving sales to Dynamics 365?

What engagement history migrates from Touchdown?

Related migrations to explore

Move from Touchdown. Land in Microsoft Dynamics 365 Sales , intact.

Move from Touchdown.
Land in Microsoft Dynamics 365 Sales , intact.