Data Management Framework (DMF)

The Data Management Framework (DMF) is the Dynamics 365 Finance and Supply Chain Management tool for bulk data movement. It centres on data entities — denormalised, versioned views of one or more underlying tables — that are imported or exported through data projects. DMF handles initial customer migrations, ongoing batch ETL, and recurring integrations through scheduled file drops or HTTP endpoints. Composite entities import related tables in a single transactional unit. DMF is the heavy-batch counterpart to Dual-write (synchronous near-real-time sync) and is used heavily during data migration cycles and for high-volume scheduled integrations.

In practice, a data entity is the layer that makes DMF usable without knowing F&O's underlying normalised table structure — a single "Customers V3" entity, for instance, presents a flat, business-friendly view that under the hood writes to several related tables in the right order and with the right validation. Building a migration or integration against data entities rather than raw tables is almost always the right call, since Microsoft maintains the entity's mapping across platform updates in a way a hand-written direct-table integration would not survive.

Where confusion arises: DMF and dual-write solve genuinely different problems and are not interchangeable — DMF is built for scheduled or one-off bulk movement (a nightly batch file, a one-time cutover load) where near-real-time latency doesn't matter, while dual-write exists specifically for scenarios needing the two systems to reflect each other within seconds. A project moving large historical volumes for a cutover reaches for DMF; a project keeping Sales and Finance customer records in sync as users work reaches for dual-write. Using DMF for a genuinely real-time need means building a polling job to fake immediacy DMF was never designed to provide.