[{"data":1,"prerenderedAt":404},["ShallowReactive",2],{"blog-\u002Fblog\u002Fcutover-and-go-live-for-finance-systems":3,"blog-related-\u002Fblog\u002Fcutover-and-go-live-for-finance-systems":379,"blog-surround-\u002Fblog\u002Fcutover-and-go-live-for-finance-systems":403},{"id":4,"title":5,"audience":6,"body":10,"cluster":341,"conversionGoal":342,"cornerstone":343,"date":344,"description":345,"draft":346,"extension":347,"factCheckedAt":348,"faq":349,"featured":346,"language":348,"meta":359,"minRead":360,"navigation":343,"order":361,"originalAsset":348,"path":362,"pillar":363,"primaryKeyword":364,"publicationOrder":365,"relatedProject":348,"releaseScope":348,"reviewCycle":366,"reviewMethod":348,"reviewStatus":367,"reviewedAt":348,"reviewedBy":368,"searchIntent":369,"seo":370,"sources":348,"stem":371,"tags":372,"type":376,"updated":377,"__hash__":378},"blog\u002Fblog\u002Fcutover-and-go-live-for-finance-systems.md","Cutover and Go-Live for Finance Systems",[7,8,9],"engineering-manager","finance-transformation-lead","solution-architect",{"type":11,"value":12,"toc":328},"minimark",[13,36,41,56,60,63,85,95,99,106,110,118,142,153,157,169,173,202,206,209,235,239,246,254,258,294,301,312,315],[14,15,16,26,27,31,32,35],"p",{},[17,18,19,20,25],"strong",{},"Cutover is the ",[21,22,24],"a",{"href":23},"\u002Fblog\u002Fagile-vs-waterfall-for-finance-systems-delivery","tightly-planned transition"," from the old system to the new one — migrating the data, switching over, and going live — usually inside a short, high-stakes window."," Go-live is the moment within it when the new system becomes the system of record. For finance systems, cutover is dominated by two things: getting the ",[28,29,30],"em",{},"opening balances exactly right",", and timing the whole thing around ",[28,33,34],{},"period-end"," so the books are clean. It's the phase where months of good work are either landed safely or undone in a weekend — which is why it's run from a rehearsed runbook, not improvised.",[37,38,40],"h2",{"id":39},"what-cutover-and-go-live-are","What cutover and go-live are",[14,42,19,43,46,47,51,52,55],{},[28,44,45],{},"sequence"," that takes you from \"built and ",[21,48,50],{"href":49},"\u002Fblog\u002Fuser-acceptance-testing-for-finance-systems","tested","\" to \"live, old system retired.\" Go-live is the ",[28,53,54],{},"point of no return"," inside that sequence — gated by a formal go\u002Fno-go decision. Everything before go-live is reversible; everything after commits you to the new system for real.",[37,57,59],{"id":58},"why-finance-cutover-is-high-stakes","Why finance cutover is high-stakes",[14,61,62],{},"Most systems start empty. Finance systems start with the entire past carried forward:",[64,65,66,73,79],"ul",{},[67,68,69,72],"li",{},[17,70,71],{},"Opening balances must be exact."," Every account balance in the new system has to tie, to the penny, to the old one at the cut. A wrong opening balance corrupts every report from day one.",[67,74,75,78],{},[17,76,77],{},"Open items can't be lost."," In-flight invoices, unreconciled payments, open deals — miss one and it simply vanishes from the books, surfacing months later as an unexplained difference.",[67,80,81,84],{},[17,82,83],{},"The window is narrow."," Finance cuts over around a period boundary, so the migration, reconciliation and checks are compressed into the few days the books are quiet.",[86,87,88],"pull-quote",{},[14,89,90,91,94],{},"Most systems go live empty and fill up. Finance systems go live ",[28,92,93],{},"full"," — with every balance and open item carried across — which is why the migration, not the software, is where cutover succeeds or fails.",[37,96,98],{"id":97},"the-cutover-plan-is-a-runbook","The cutover plan is a runbook",[14,100,101,102,105],{},"A cutover plan is not a milestone in a Gantt chart — it's a ",[17,103,104],{},"runbook",": a minute-by-minute sequence of tasks, each with a timing, an owner, a dependency, and a done-check. \"Extract balances from legacy (Fri 18:00, owner: X), load to new (Fri 20:00, owner: Y), reconcile (Sat 09:00, owner: Z)…\" The plan's job is that on the day, nobody is improvising — they're executing a script that's already been proven.",[37,107,109],{"id":108},"data-migration-is-the-core","Data migration is the core",[14,111,112,113,117],{},"The bulk of finance cutover is ",[21,114,116],{"href":115},"\u002Fblog\u002Fdata-migration-for-finance-systems","data migration",", in three layers:",[64,119,120,130,136],{},[67,121,122,125,126,129],{},[17,123,124],{},"Master data"," — accounts, entities, bank details, counterparties, standing instructions. Migrated and validated ",[28,127,128],{},"first",".",[67,131,132,135],{},[17,133,134],{},"Opening balances"," — the carried-forward position at the cut.",[67,137,138,141],{},[17,139,140],{},"Open items"," — the in-flight transactions that must continue their life in the new system.",[14,143,144,145,148,149,129],{},"And the non-negotiable rule: ",[17,146,147],{},"reconcile every migrated layer."," Migration isn't done when the data loads; it's done when the loaded data is proven equal to the source. Counts and control totals, source versus target, exactly as with any ",[21,150,152],{"href":151},"\u002Fblog\u002Finterface-monitoring-and-reconciliation","interface",[37,154,156],{"id":155},"timing-around-period-end","Timing around period-end",[14,158,159,160,163,164,168],{},"Finance cuts over at a ",[17,161,162],{},"period boundary"," — ideally right after a close — so there's a clean line: the old system owns everything up to the cut, the new system owns everything after. Cutting over mid-period means splitting a period across two systems, which turns ",[21,165,167],{"href":166},"\u002Fblog\u002Fhypercare-and-post-go-live-stabilization","the first close"," into a reconciliation nightmare. Pick the boundary, and protect it.",[37,170,172],{"id":171},"the-gono-go-decision","The go\u002Fno-go decision",[14,174,175,176,179,180,183,184,188,189,193,194,197,198,129],{},"Before go-live, a ",[17,177,178],{},"go\u002Fno-go"," checkpoint: against pre-agreed criteria — migration reconciled, critical checks passed, ",[21,181,182],{"href":49},"UAT signed off",", ",[21,185,187],{"href":186},"\u002Fblog\u002Foperational-readiness-and-acceptance","operational readiness proven"," — the accountable owners decide, explicitly, to proceed or not: a ",[21,190,192],{"href":191},"\u002Fblog\u002Fgovernance-and-steering-for-finance-programmes","governance decision"," in its own right. The value is having defined the criteria ",[28,195,196],{},"in advance",", so the decision is made against a standard, not against how tired everyone is at 2am. The same discipline transfers, almost unchanged, to promoting an AI step into production — see ",[21,199,201],{"href":200},"\u002Fblog\u002Fai-pilot-exit-criteria","what a pilot has to prove first",[37,203,205],{"id":204},"rehearse-it-and-plan-the-fallback","Rehearse it, and plan the fallback",[14,207,208],{},"Two things separate calm cutovers from disasters:",[64,210,211,225],{},[67,212,213,216,217,220,221,224],{},[17,214,215],{},"A dress rehearsal."," At least one full ",[17,218,219],{},"mock cutover"," on a copy — run the entire runbook end to end, time it, find what breaks. The real cutover should be the ",[28,222,223],{},"second"," time you've done it, not the first.",[67,226,227,230,231,234],{},[17,228,229],{},"A fallback plan."," A defined way back if go\u002Fno-go fails or something breaks past the point of proceeding. Knowing you ",[28,232,233],{},"can"," revert is what makes the go decision safe to take.",[37,236,238],{"id":237},"hypercare-after-go-live","Hypercare after go-live",[14,240,241,242,245],{},"Go-live isn't the end — it's the start of ",[17,243,244],{},"hypercare",": a period of heightened support right after, when the real users hit real edge cases and need fast help. Staff it deliberately. The first close on the new system is the true test, and it's where issues the whole project missed finally show up.",[247,248],"diagram",{":stages":249,"caption":250,"desc":251,"kind":252,"title":253},"[{\"label\":\"Built and tested\"},{\"label\":\"Mock cutover\",\"note\":\"Run the entire runbook end to end, time it, find what breaks. The real cutover should be the second time you've done it, not the first.\"},{\"label\":\"Migrate master data, then opening balances, then open items\",\"note\":\"Reconcile every migrated layer — counts and control totals, source versus target — at a period boundary, ideally right after a close.\"},{\"label\":\"Go\u002Fno-go\",\"gate\":true,\"note\":\"Against pre-agreed criteria — migration reconciled, critical checks passed, UAT signed off, operational readiness proven — plus a defined way back if it fails.\"},{\"divider\":\"point of no return\"},{\"label\":\"Go-live\",\"note\":\"The moment the new system becomes the system of record.\"},{\"label\":\"Hypercare\",\"note\":\"Heightened support while real users hit real edge cases. The first close on the new system is the true test.\"},{\"label\":\"Live, old system retired\"}]","Everything before go-live is reversible; everything after commits you to the new system for real.","A rehearsed mock cutover and a reconciled three-layer migration precede a go\u002Fno-go decision. Go-live is the point of no return, after which hypercare runs until the old system is retired.","stages","The cutover sequence, from built and tested to old system retired",[37,255,257],{"id":256},"what-goes-wrong-on-cutover-weekend","What goes wrong on cutover weekend",[64,259,260,270,276,282,288],{},[67,261,262,265,266,269],{},[17,263,264],{},"Unrehearsed cutover."," The runbook's first real run ",[28,267,268],{},"is"," the live one, so the surprises land at the worst possible moment.",[67,271,272,275],{},[17,273,274],{},"Unreconciled migration."," Data loaded but not proven equal to source, so a wrong opening balance is discovered weeks later in the books.",[67,277,278,281],{},[17,279,280],{},"No go\u002Fno-go criteria."," The decision to proceed is made on optimism and fatigue, not evidence.",[67,283,284,287],{},[17,285,286],{},"No fallback."," No way back, so a failing cutover has to be pushed forward regardless.",[67,289,290,293],{},[17,291,292],{},"Cutting over mid-period."," No clean boundary, so the first close spans two systems and reconciles to nothing.",[14,295,296,297,300],{},"Run cutover from a rehearsed runbook, migrate and ",[28,298,299],{},"reconcile"," every layer, cut at a period boundary, gate go-live with real go\u002Fno-go criteria, keep a fallback, and staff hypercare — and the riskiest weekend of the project becomes a controlled, boring success. Which, for a finance go-live, is exactly what you want it to be.",[14,302,303,306,307,311],{},[17,304,305],{},"Work the gate:"," the free ",[21,308,310],{"href":309},"\u002Ftools\u002Fcutover-go-live-checklist","Cutover & Go-Live Readiness Checklist"," turns this into a live go\u002Fno-go — the critical items gate the verdict, and it never shows GO until open items are owned and an authorized owner has actually decided.",[313,314],"hr",{},[14,316,317],{},[28,318,319,320,323,324,129],{},"See also ",[21,321,322],{"href":49},"user acceptance testing"," and ",[21,325,327],{"href":326},"\u002Fblog\u002Ffit-gap-analysis-for-finance-systems","fit-gap analysis",{"title":329,"searchDepth":330,"depth":330,"links":331},"",2,[332,333,334,335,336,337,338,339,340],{"id":39,"depth":330,"text":40},{"id":58,"depth":330,"text":59},{"id":97,"depth":330,"text":98},{"id":108,"depth":330,"text":109},{"id":155,"depth":330,"text":156},{"id":171,"depth":330,"text":172},{"id":204,"depth":330,"text":205},{"id":237,"depth":330,"text":238},{"id":256,"depth":330,"text":257},"execution","cutover-checklist",true,"2026-07-23","Finance system cutover is the tightly-planned transition from old to new — migration, switchover, go-live — in a short, high-stakes window.",false,"md",null,[350,353,356],{"question":351,"answer":352},"What is cutover in a system implementation?","Cutover is the tightly-planned transition from the old system or process to the new one — migrating the data, switching over, and going live — usually within a short, high-stakes window. It's the sequence of steps that takes you from 'the new system is built and tested' to 'the new system is live and the old one is retired,' and it's governed by a detailed runbook of tasks, timings and owners.",{"question":354,"answer":355},"What is the difference between cutover and go-live?","Cutover is the whole transition process — the migration, the switchover steps, the reconciliation, the checks. Go-live is the specific moment within it when the new system becomes the system of record and the business starts using it for real. Cutover is the journey; go-live is the point of no return along it, usually gated by a formal go\u002Fno-go decision.",{"question":357,"answer":358},"Why is cutover so critical for finance systems?","Because finance carries balances forward, so the opening position in the new system has to be exactly right — every account balance, every open item, every in-flight payment migrated and reconciled to the penny. A lost open invoice or a wrong opening balance corrupts the books from day one and can take months to unwind. Finance cutover is also timed tightly around period-end to get a clean cut, which compresses everything into a narrow, unforgiving window.",{},6,7,"\u002Fblog\u002Fcutover-and-go-live-for-finance-systems","finance-systems-delivery","finance system cutover",35,"annual","reviewed","Tan Gravam","informational",{"title":5,"description":345},"blog\u002Fcutover-and-go-live-for-finance-systems",[373,374,375],"delivery","finance-systems","implementation","text","2026-07-29","xnDOirkv9J2JfQkr0ZhNkBo-U5e-3oGzAOdY15ODRq0",{"related":380,"prev":392,"next":396,"hasOrder":343,"place":398},[381,385,389],{"path":382,"title":383,"description":384},"\u002Fblog\u002Fdefect-triage-and-exit-criteria","Defect Triage & Exit Criteria for Finance Go-Lives","How to run defect triage on a finance-system project: severity vs priority, blockers, accepted defects and workarounds, and the exit criteria that gate go-live.",{"path":386,"title":387,"description":388},"\u002Fblog\u002Fchange-management-for-finance-system-rollouts","Change Management for Finance System Rollouts","A technically perfect finance system fails if the team won't adopt it. Change management wins that adoption — why finance resists, and how to get it.",{"path":186,"title":390,"description":391},"Operational Readiness & Acceptance for Finance Systems","Passing go-live isn't being ready to run. How to prove operational readiness — support, monitoring, runbooks, ownership — and get acceptance before handover.",{"path":393,"title":394,"type":395,"language":348},"\u002Fblog\u002Ftest-data-management","Test Data Management for Finance-System Projects","pattern",{"path":115,"title":397,"type":376,"language":348},"Data Migration for Finance Systems",{"label":399,"position":400,"total":401,"hub":402},"Execution",9,13,"\u002Ftopics\u002Ffinance-systems-delivery",[],1787475401838]