Migrate your Touchdown data
B2B marketing automation CRM offering contact management, segmentation, and campaign creation at an entry-level price point. Positioned between lightweight email tools and enterprise marketing platforms.
In its favor
Why people choose Touchdown
The signal that keeps Touchdown on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Native, in-CRM integration with Microsoft Dynamics 365, Power Apps, and Business Central — Touchdown runs inside the CRM rather than requiring two-way sync, so contact data never leaves the Microsoft environment.
Single-vendor marketing suite covering email, SMS, landing pages, forms, event management, and sales automation — useful for Dynamics customers filling the marketing gap left after Dynamics 365 Marketing was rebranded/retired.
GDPR-aligned, Europe-hosted data residency, which simplifies procurement for EU customers who would otherwise need data-processing agreements with US-hosted alternatives.
Entry-level pricing positioned for SMBs (starting around $49/user/month per the existing tier) — a lower-cost option than Microsoft's own marketing add-on or larger automation suites like Marketo or HubSpot.
Drag-and-drop email and landing page editor with prebuilt responsive templates, lowering the build cost for small marketing teams without dedicated designers.
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.
Reasons to switch
Why people leave Touchdown
The recurring reasons buyers give for replacing Touchdown. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Touchdown fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Touchdown pricing overview
Touchdown uses a per-user monthly pricing model starting at $49 per user per month. The base tier includes 10,000 emails annually with contact management, segmentation, and campaign tools.
Standard
Tier 1 of 1
$49/user/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Touchdown's schedule — see our quote-based pricing →
What gets migrated
Touchdown object support
Object-by-object support for Touchdown migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContact management is explicitly listed as a core feature on Gartner Peer Insights. Contacts migrate 1:1 with standard field mapping. We handle email addresses, names, and custom contact properties during migration.
Campaigns
Mapping requiredCampaign creation is a core capability per Gartner. Campaign metadata and audience assignments transfer but require field mapping since campaign structures vary between marketing automation platforms. We preserve campaign history and linked contacts during the transfer.
Companies/Accounts
Mapping requiredStandard in most CRMs but not explicitly confirmed in Touchdown documentation. We treat Company records as mapping work and confirm schema discovery during the pre-migration API exploration phase.
Segments
Mapping requiredSegmentation capability is listed on Gartner but the segment object schema is undocumented. We discover segment definitions via API and recreate them in the destination platform using equivalent filter logic.
Email Templates
Mapping requiredPersonalized messaging tools exist per Gartner but template storage format is not published. We export template content and associated merge fields, then map them to the destination's template structure.
Custom Fields
Mapping requiredMarketing automation platforms typically support custom fields but Touchdown's custom field schema is not publicly documented. We discover custom fields during API exploration and handle type conversion at migration time.
Activities/Engagements
Mapping requiredEngagement tracking is implied by the personalized messaging feature set. Activity history migration requires schema discovery per customer instance before we can map opens, clicks, and sends.
Users/Owners
Mapping requiredUser assignment is standard in CRMs but we treat owner records as mapping work since Touchdown's user object schema is not published. We map users to corresponding destination users during import.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contact management is explicitly listed as a core feature on Gartner Peer Insights. Contacts migrate 1:1 with standard field mapping. We handle email addresses, names, and custom contact properties during migration. |
| Campaigns | Mapping required | Campaign creation is a core capability per Gartner. Campaign metadata and audience assignments transfer but require field mapping since campaign structures vary between marketing automation platforms. We preserve campaign history and linked contacts during the transfer. |
| Companies/Accounts | Mapping required | Standard in most CRMs but not explicitly confirmed in Touchdown documentation. We treat Company records as mapping work and confirm schema discovery during the pre-migration API exploration phase. |
| Segments | Mapping required | Segmentation capability is listed on Gartner but the segment object schema is undocumented. We discover segment definitions via API and recreate them in the destination platform using equivalent filter logic. |
| Email Templates | Mapping required | Personalized messaging tools exist per Gartner but template storage format is not published. We export template content and associated merge fields, then map them to the destination's template structure. |
| Custom Fields | Mapping required | Marketing automation platforms typically support custom fields but Touchdown's custom field schema is not publicly documented. We discover custom fields during API exploration and handle type conversion at migration time. |
| Activities/Engagements | Mapping required | Engagement tracking is implied by the personalized messaging feature set. Activity history migration requires schema discovery per customer instance before we can map opens, clicks, and sends. |
| Users/Owners | Mapping required | User assignment is standard in CRMs but we treat owner records as mapping work since Touchdown's user object schema is not published. We map users to corresponding destination users during import. |
Gotchas
What to watch for in Touchdown migrations
Issues we've hit on past Touchdown migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Catalog website appears mismatched
Touchdown stores its data inside the Dynamics 365 / Dataverse tenant
SMS data and consent records require careful handling
Templates and landing pages reference Microsoft-hosted assets
| Severity | Issue |
|---|---|
| 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 |
Leaving Touchdown?
Where Touchdown customers move next
12 destinations Touchdown can migrate to.
How a Touchdown migration works
Four steps, Touchdown-specific
Connect
Touchdown does not publish a standalone public API. Because it operates as a Dynamics 365 / Power Platform solution, programmatic access to its data goes through the Microsoft Dataverse Web API using Microsoft Entra ID (Azure AD) OAuth 2.0 against the customer's tenant. into Touchdown. Scopes limited to read-only on the data we move.
Map
We translate Touchdown-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Touchdown quirks before production.
Migrate
Full migration with Touchdown rate-limit handling. Rollback available throughout.
FAQ
Touchdown migration FAQ
Answers to the questions buyers ask most during Touchdown migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Touchdown migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Touchdown.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Touchdown setup and destination — written quote back within a business day.