Month-end as a modernization constraint
Why cutover plans that ignore closing calendars fail, and how to schedule strangler work around lodgement dates.
Engineering teams like Tuesday deploys. Finance teams live inside closing calendars. In Australian organisations that still lodge on fixed cycles, a modernization plan that treats month-end as “just another regression suite” will lose political support the first time numbers disagree.
Map the calendar before the modules
List every process that cannot slip: payroll, BAS-related extracts, stock valuation, membership renewals. Tie each to the legacy path that produces it. Those paths become the spine of your risk register.
Rehearse with real volumes
Staging data that never includes end-of-month spikes will miss rounding and timeout failures. Borrow anonymised production-shaped sets where policy allows, and run a rehearsal while operators watch.
Keep a boring fallback
Strangler patterns work when the old path can still print the run sheet or post the journal for one more cycle. Romantic “big bang” cutovers belong in novels, not in warehouses.
Our legacy modernization engagement always asks for the closing calendar in week one. If you do not have it written down, that is the first workshop artefact.