Migrate from Tofu to Microsoft Dynamics 365 Sales

Tofu Accounts (target companies in the ABM model) map directly to Microsoft Dynamics 365 Account records. We export Account name, industry, tier, owner, and any custom enrichment fields from Tofu and write them to the corresponding Account fields in Dynamics. Tofu does not use a separate Company object — Accounts serve both the company identification and targeting role. The primary Account name becomes Account Name, and any tier classification (Enterprise, Mid-Market, SMB) migrates as a custom Account field for segmentation in Dynamics reporting.

Tofu Campaigns are top-level containers for landing pages, email sequences, ads, and collateral tied to a targeting strategy. We export all campaign metadata and status. On Sales Enterprise ($105/user/mo), we recommend a custom CampaignExtension entity that captures ABM-specific fields (target account tier, ICP fit score, campaign intent signals). On Sales Professional ($65/user/mo), Dynamics native Campaign records handle the container but lack ABM-specific fields; we store those as custom fields on the Campaign record.

Tofu Playbooks encode multi-step outreach sequences with branching logic, timing, and channel rules. Microsoft Dynamics 365 Sales has no native multi-step cadence or branching playbook object. We decompose each Tofu Playbook into discrete Step records and import them as a linked series of Task records with a custom PlaybookId lookup, step_order, channel type, delay_days, and condition_branch fields preserved as custom Task fields. Any branching conditions that cannot be represented linearly are flagged in a PlaybookBranchMap__c custom field for manual Power Automate rebuild.

Tofu Personas define the ICP profile — industry, role, pain points, and messaging tone — used to personalize content per target account. We export persona definitions as structured records and map them to custom fields on the Dynamics Account: Persona_Role__c, Persona_IndustryFocus__c, Persona_PainPoints__c, and Persona_MessagingTone__c. If a single Tofu Persona applies to multiple Accounts, we populate these custom fields on each linked Account record. Dynamics does not have a native Persona object, so this flattening into Account-level custom fields is the standard migration pattern.

Tofu Content Assets include landing pages, one-pagers, ads, and sales collateral generated by the AI. We export asset metadata (name, version, creation date, linked Campaign and Account associations) and write it to a SharePoint document library provisioned within the Microsoft Dynamics 365 Sales environment or as Notes attached to the related Account or Campaign record. The binary files (PDFs, images, landing page URLs) are re-downloaded from Tofu's CDN asset URLs at export time. If Tofu rotates asset URLs post-migration, we re-validate each URL in a pre-flight check before final sync.

Tofu Audiences are filtered subsets of Accounts or Contacts used to trigger Playbook activation. We export audience membership as a list of Account IDs with the filter criteria preserved in a custom Audience entity (AudienceId, Name, FilterCriteria__c, CreatedDate). Microsoft Dynamics 365 Sales does not have a native Audience object. Each membership record links to an Account via a lookup relationship. The filter criteria are stored as a JSON or text field so the customer's Dynamics admin can recreate the audience as a static Marketing List or a dynamic segment in Dynamics Customer Insights Journeys post-migration.

Tofu supports custom fields on Accounts, Campaigns, and Playbooks. We detect any non-standard properties during the pre-migration schema scan and map them to equivalent custom fields in Dynamics 365. Custom field types are mapped: Tofu text to Dynamics Single-Line Text or Multi-Line Text, Tofu number to Decimal or Whole Number, Tofu date to Date, and Tofu dropdown to Option Set. We create the custom fields in Dynamics before migration begins so that data lands in typed fields rather than generic note fields.

Users in Tofu are assigned as Campaign owners and Playbook creators. We export user email addresses and names and map them to SystemUser records in Dynamics 365. We resolve by email match against the destination org's Azure Active Directory-backed user table. Any Tofu Owner without a matching SystemUser goes to a reconciliation queue for the customer's Dynamics admin to provision before record import resumes, as OwnerId references are required on Campaign, Account, and Activity records.