Why Lasernet migrations happen
A migration is rarely the goal in itself. It is usually triggered by something else: a move to Dynamics 365, an ERP upgrade, retiring an older reporting or print tool, consolidating environments or updating Lasernet itself. Because documents are the visible output of every process, they need to work from the first day after the change.
Start with an inventory
List every document that is produced today: what it is, how it is triggered, how often, in which languages, who receives it and who owns it. It is common to find documents no one has used for years, and a few that nobody realized were critical. The inventory becomes the scope and the test plan.
Decide what to retire, keep or redesign
For each document, decide whether to retire it, migrate it as it is or redesign it. Copying everything exactly preserves old workarounds. Redesigning everything is expensive. A document-by-document decision, made with the business owner, is usually the right balance.
Plan for data and integration changes
When the source ERP changes, the data a document receives changes too. Field names, structures and codes may differ. Map each field carefully and confirm that the new system provides everything the document needs. Where it does not, plan the Dynamics 365 development work early.
Test with real data
Run realistic data through old and new versions and compare the results field by field. Ask business users to approve samples for each document type, including unusual cases: long text, foreign addresses, credit notes and partial deliveries.
Cutover and support
Write down the cutover steps, including how you will switch, who confirms success and what the fallback is. Plan extra support for the first days and the first month-end. Our Lasernet migration service follows this structure.
A short checklist
- Complete inventory with owners and priorities.
- Decision for each document: retire, migrate or redesign.
- Field mapping and gap list for the new data source.
- Approved test samples for every document type.
- Rehearsed cutover plan and fallback.
- Support arrangements for the first weeks.
Talk to a specialist
If this topic is relevant to a project you are planning, we are happy to discuss it.
