Migrating Legacy Data into Finance and Operations Apps
Short answer
BD Use a public data entity with the Excel add-in, or a data entity with a Data Management import job, to load the legacy and vendor data into finance and operations apps.
Question
Which two options can you use? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Key Takeaways
The question tests whether you can distinguish inbound data-loading mechanisms from outbound analytics repositories, and the trap is choosing BYOD or Entity store because they are also built on data entities.
For loading legacy and vendor-supplied data into Dynamics 365 finance and operations apps, only data entity based inbound paths qualify: a public data entity used through the Excel add-in, and a data entity driven Data Management import job. BYOD and Entity store are outbound analytical stores, so they cannot satisfy a migration requirement.
Common mistake: The most common wrong pick is A (data entity and BYOD). Learners see that BYOD is built on data entities and assume it supports migration, but BYOD only exports entity data to an external SQL database for analytics, data warehousing and batch reporting integration, so nothing is loaded into the finance and operations database.
Expert Analysis
Why the Answer Is Correct
A public data entity exposed through OData can be consumed by the Excel add-in, which lets an authorized user load or maintain records in finance and operations apps, and the same data entity can be staged and loaded through a Data Management import job for file- or package-based bulk migration. Together these two options are complete inbound solutions: one interactive and suited to smaller reference sets such as a vendor exclusion list, the other the supported high-volume path for full legacy data migration. Both use the standard data entity framework, which is the sanctioned mechanism for moving data into the application database.
Why the Other Options Are Wrong
Bring your own database (BYOD) exports entity data from finance and operations to an external SQL data warehouse for reporting and analytics; it never writes data back, so it cannot implement a migration. Entity store is an embedded analytical data lake (a Data Lake-backed workspace of aggregated entities) used for Power BI and embedded reports, and like BYOD it is a read-only consumption repository for outbound data. Option C pairs a data entity with Entity store, and option A pairs a data entity with BYOD, so in both cases the second half disqualifies the pair even though the data entity half is valid. Community consensus is also relevant here but the reasoning above, not the vote, is what settles it.
Community Comment Notes
Most voters converge on B and D, with phamvanphuong1501 simply labeling them as the options that "import into D365" and AbhiN1106 correctly noting that "BYOD and Entity store are outbound analytical export repositories only." javism1106 adds a practical caveat, saying "I would not recommend Excel (Odata) for migration purposes," which is sound production advice but does not change exam correctness since Excel still presents a complete solution. yuri_rusanov's phrasing that the scenario calls for a "(public) data entity for their legacy system, Excel add-in for their vendor exclusion list access" matches the option wording directly. One dissenter, sadoki9311, chose A and B, but that choice is inconsistent with BYOD being export-only.
Exam Strategy
In MB-500 migration questions, immediately classify each mechanism as inbound (writes into the F&O database) or outbound (export/analytical). BYOD and Entity store are always outbound, so any option containing them is wrong for a migration requirement.
Frequently Asked Questions
Why is BYOD not a valid option for this migration requirement?
Can Entity store be used to migrate legacy data into Dynamics 365?
Is the Excel add-in really appropriate for migrating data?
Discussion 9 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 9
-
phamvanphuong1501 👍 31B & D (import into D365)
-
Ahmed_Hassan 👍 6BYOD feature is for Analytics, data warehousing and for batch integrations Entity store enables Power Bi integration so the answers are B & D
-
UmarAli 👍 2B and D are correct answer
-
faycal 👍 2answer is B & D
-
AbhiN1106 👍 1Data Management import jobs handle bulk migrations via files/packages; the Excel add-in allows importing smaller reference sets. BYOD and Entity Store are outbound analytical export repositories only
Show 4 more comments
-
yuri_rusanov 👍 1(public) data entity for their legacy system, Excel add-in for their vendor exclusion list access and Entity store for their Power BI reports. Dump answer seems alright to me.
-
javism1 👍 1B&D are valid, although I would not recommend Excel (Odata) for migration purposes
-
sadoki9311 👍 1This should be A & B
-
globeearth 👍 1Agreed
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All MB-500 Questions
Access 115 questions with complete answers and detailed explanations.
View Full MB-500 Practice Test →