Share
Report
84Hi Experts,
We have a client with a planned Go-Live on 1st May, and we are currently in the process of planning the data migration strategy from 1st January onwards.
We would like guidance on the most appropriate approach for this scenario:
- Should we migrate only opening balances as of 30th April, or should we also consider migrating detailed transactions (Jan–Apr)?
- If transactions are to be migrated, what would be the recommended approach for the following:
- Purchase Orders
- Purchase Invoices
- Sales Invoices
- General Ledger transactions
- Item/Inventory balances
- In case of transaction-level migration:
- How should the data be uploaded in Business Central (recommended sequence and tools)?
- How can we ensure proper reconciliation between legacy system and Business Central?
- Specifically for inventory:
- How should inventory balances (quantity and value) be brought into the system?
- How should additional costs (freight, charges, adjustments) be handled during migration?
- What is the recommended approach for:
- Open vs closed transactions
- Ensuring accurate AR/AP aging
- Matching trial balance and subledgers (GL vs Customer/Vendor vs Inventory)
From our understanding, one common approach is to migrate:
- Master data
- Opening balances
- Open transactions (AR/AP/PO/SO)
while keeping historical closed transactions in the legacy system, as full historical migration can be complex and time-consuming ()
However, we would like to understand:
- In which scenarios detailed transaction migration (Jan–Apr) is recommended
- And how to execute it correctly without reconciliation issues
It would be very helpful if someone could share a detailed, practical approach or real-life implementation experience, including examples or best practices followed during similar go-live scenarios.
Thanks in advance!
Categories:
I have the same question (0)
All responses (
Answers (
