A 16-year system finally hit its limit
Toyota Finance Australia ran its core finance operations on SAP ECC for 16 years before retiring it this past August. The lender, which handles vehicle loans, dealer financing, and fleet services, is not a company known for chasing new technology for its own sake. That makes the timing instructive. The project, internally named Project Kizuna, replaced the ECC environment with SAP S/4HANA Cloud Public Edition, and Moulik Doshi, the company's head of financial reporting and operations, walked through the details at the SAP NOW AI Tour in Sydney on August 12, 2026. iTnews covered the session on November 4.
The headline number is the timeline: 13 months from project start to go-live. For a CIO sitting on an ECC estate with no migration plan yet, that figure is worth anchoring on. It is not a greenfield implementation with months of requirements workshops bolted on. It is a defined-scope move from an on-premises core to a public cloud edition of the same vendor's platform, and it still took more than a year to execute safely around a live finance operation. Project Kizuna name aside, the company has said little publicly about budget or headcount committed to the effort, which is typical of these announcements and a reminder that a published timeline rarely comes with the full cost picture attached.
The deadline driving every ECC conversation
SAP's own maintenance calendar is the forcing function here, not enthusiasm for cloud ERP. Mainstream maintenance for the latest three ECC 6.0 enhancement packages runs out in 2027. Customers can buy optional extended maintenance, but only through 2030. For a CIO who has been deferring the ECC conversation because the current system still works, that is a four-year window at the outside, and a one-year window before the cheaper support tier disappears.
Toyota Finance Australia's 13-month execution window gives a rough sense of what fitting inside that deadline actually requires in practice. A finance organization that waits until the 2027 maintenance cliff to start scoping will be executing under far more schedule pressure than a team that treats 2026 as the last comfortable planning year. The lesson is less about SAP specifically and more about any vendor-imposed end-of-support date: the real deadline is the one that leaves room for a competent, non-heroic project, printed nowhere in the support contract but felt in every rushed go-live. Work backward from 13 months plus a buffer for vendor selection and internal sign-off, and the last safe start date for a 2027 cutover has effectively already passed for most ECC shops that have not begun.
What public cloud forces you to give up
Moving from ECC to S/4HANA Cloud Public Edition is not a lift-and-shift. The public cloud edition runs on SAP's standard, multi-tenant configuration, which means years of ECC customizations do not simply carry over. Whatever process modifications Toyota Finance Australia built up over 16 years had to be reconciled against SAP's out-of-the-box flows, accepted, replaced, or in some cases dropped. That reconciliation work, more than the technical data migration, is typically where these projects consume time and budget.
This is the trade-off every CIO evaluating a public cloud ERP edition needs to price in honestly. You gain faster patching, lower infrastructure overhead, and a cleaner upgrade path, because the vendor controls the configuration surface. You give up the ability to bend the system to match a legacy business process that your organization may have simply gotten used to rather than actually needing. Toyota Finance Australia's willingness to make that trade is itself a data point about how much customization a finance back office truly requires once someone is forced to ask.
Self-service reporting arrived before the organization did
The one concrete capability change Doshi described is that finance users can now build their own views of ERP data, rather than routing report requests through IT or a BI team. On paper, that is exactly the kind of decentralization CIOs pitch when justifying a platform modernization: reduce the backlog on the technical team, put reporting power closer to the people who need the numbers, and free data analysts from being a permanent bottleneck for routine finance questions. It is the kind of line that reads well in a board update and even better in a business case built to justify the migration's cost in the first place.
In practice, Doshi said the organization is still learning how to use the platform, which is a more honest status update than most vendor case studies offer. Self-service reporting tools do not automatically produce self-service reporting literacy. The gap between having the capability and having finance staff who know how to build a correct, trustworthy view without IT oversight is an adoption project in its own right, usually underestimated in the original business case and rarely funded as its own line item. A CIO who signs off on this kind of migration expecting an immediate productivity gain in reporting should instead budget for a second, quieter phase: training, governance rules for who can publish a self-built view as an official number, and time for finance staff to build confidence before they are trusted to skip the old request-and-wait process entirely.
What this means for the build-versus-wait decision
If your organization is running ECC and has not yet committed to a path off it, Toyota Finance Australia's project offers a usable reference point rather than a marketing claim. Thirteen months, for a finance-focused scope, moving to the public cloud edition of the same vendor's suite, is achievable without being trivial. That is a more defensible planning number than either the optimistic 6-month pitch from an implementation partner or the open-ended multi-year horror story that makes every ECC migration sound unapproachable.
The decision CIOs actually face is not simply when to migrate. It is whether to take the public cloud edition's standardization trade now, while there is runway to manage it deliberately, or to wait for the 2027 and 2030 maintenance deadlines to compress the decision into a forced, under-resourced sprint. Toyota Finance Australia chose to move while it still had a choice, weighing that path against staying on a more customizable private S/4HANA deployment or deferring the question entirely to a systems integrator's roadmap built around billable hours rather than an internal deadline. That sequencing, more than the specific product chosen, is the part of this story worth taking back to your own ERP roadmap, and it sets a baseline every competing proposal on your desk should now be measured against: just over a year, for a finance-centric scope, if you start while you still have the runway to do it deliberately.
