Case Study - Large-scale Data Migration:
"A company is consolidating several legacy systems into D365 F&O. They need to import hundreds of thousands of sales orders, purchase orders, customers, and vendors (each originally with their own numbering schemes) into F&O. Outline a migration strategy focusing on how to handle the different number sequences for these records in a way that preserves data integrity and business needs. Consider using DMF, potential custom import scripts, and whether to keep original numbers or assign new ones."
Interviewer guidance: Strong answer will discuss analyzing each entity:
- For master data like customers/vendors, possibly preserve external IDs for continuity or cross-reference (thus configure those number sequences as manual to import existing IDs without auto-generation, verifying no conflicts). [learn.microsoft.com]
- For transactional data (orders), possibly import historical records with legacy numbers to keep references (again requiring manual sequences or a temporary mapping), versus using new numbering for new transactions going forward.
- Mention using DMF for bulk import with auto-numbering where needed (especially if legacy numbers aren't required or can't be reused) and using staging if necessary to link headers and lines correctly.
- They should mention careful planning to avoid collisions, possibly using distinct sequences for legacy data vs new data (like an alternate sequence or prefix for imported historical records), and highlight any necessary testing to ensure completeness (like verifying that sequence next numbers are correct post-migration).