In my previous article, I explained why choosing the right entity matters when importing stock data into Dynamics 365 Finance & Operations — and why Inventory adjustment journal headers and lines V2 is the correct choice for initial inventory loads.
Once that decision was made, the next question was obvious:
How do I make sure the initial stock import is clearly separated from all other inventory transactions — now and in the future?
The answer lies not only in the entity, but in proper journal and number sequence design.
Why a Dedicated Journal and Number Sequence Matter
When importing initial stock, you are creating foundational inventory and financial data. These transactions are fundamentally different from day-to-day operational postings such as inventory adjustments, transfers, or corrections.
Creating:
- a dedicated inventory adjustment journal, and
- a dedicated number sequence
ensures that:
- Initial stock postings are clearly identifiable
- Audit trails remain transparent
- Finance and operations can differentiate migration data from live transactions
- Troubleshooting and reconciliation become significantly easier
In short: this setup prevents migration data from “blending in” with operational history.
Step 1: Creating a Number Sequence for Inventory Data Migration
The goal is to uniquely identify all vouchers created during the inventory data migration.
A dedicated number sequence:
- separates migration postings from operational postings
- ensures consistent and traceable voucher numbering
- supports audits and historical analysis
Configuration Steps
- Navigation: Organization administration → Number sequences → Number sequences
- Select New
- Set the following values:
- Number sequence code:
DM_Inv - Name: Data migration
- Scope: Company
- Company: Select the relevant legal entity
- Number sequence code:
- Segments:
- Optionally remove the Company segment
- Add a Constant segment with value
DM_Inv
- General:
- Continuous: Yes
- Save the number sequence
At this point, every voucher generated using this sequence will clearly indicate that it originates from the inventory data migration.
With the number sequence in place, the next step is to create a journal that is used exclusively for importing initial stock.
Step 2: Creating a Dedicated Inventory Adjustment Journal
Goal
- Import inventory balances from legacy systems
- Use standard inventory adjustment logic
- Avoid mixing migration postings with operational inventory journals
Configuration Steps
- Navigation: Inventory management → Setup → Journal names → Inventory
- Select New
- Configure the journal:
- Name:
DM_Inv - Description: Data migration – Inventory
- Journal type: Inventory adjustment
- Voucher series:
DM_Inv
- Name:
- Save the journal
This journal now serves one purpose only: initial stock migration.
Why This Setup Works
By combining:
- Inventory adjustment journal headers and lines V2
- a dedicated inventory adjustment journal
- and a dedicated number sequence
you achieve:
- Clean separation between migration data and operational data
- Predictable posting behavior using standard D365 logic
- Automatic account determination via item groups and posting profiles
- Long-term clarity for finance, auditors, and support teams
Months or even years later, anyone reviewing the data can immediately identify:
“These transactions came from the initial inventory migration.”
That level of clarity is invaluable.
Final Thoughts
Data migration is not just about getting numbers into the system — it’s about doing it in a way that remains understandable, auditable, and supportable over time.
Choosing the right entity was the first step.
Designing the right journal and number sequence is what makes the solution complete.
In Dynamics 365, small configuration decisions during migration often have long-lasting effects. This is one of those cases where doing a little more upfront pays off every day after go-live.
