# Our ERP vendor is forcing a cloud move or new version. Should we follow? Tamir Khason · Updated 2026-10-07 Treat the vendor's date as one input rather than the decision. Check what really ends on that date, what your contract says about a change this size, and what you would actually move. Following makes sense when your customizations are few or replaceable and the running cost is clear. ## Separate the vendor's date from your own need Ask in writing what ends on the support date: security fixes, legal changes, or only convenience. Ask what extended support costs, and whether a staged plan reduces the rush. A vendor-imposed platform change is also a contract event. Read the clauses on material changes, data access and termination with counsel before you talk to the vendor. Get a switching quote from one alternative, so you know what refusing would cost. ## Start with what you would actually move List your customizations, integrations and reports. For each one, decide whether the new version covers it, whether it must be rebuilt, or whether you can drop it. That list drives most of the cost and the risk. Each rebuilt customization is a future upgrade cost, and often a process nobody re-examined. Keep those tied to a real legal, customer or safety need, and ask business owners to defend the rest. Compare today's full running cost with the subscription plus the integrations and changes you would keep paying for. ## Depending on your seat If you're on the board and management brings a replacement on the vendor's timeline, ask whether the proposal compared alternatives and on what basis. Ask for the total cost and the risks of the rushed timeline. If you run IT, check that the full data history migrates and that you can export it from the new cloud in a usable form. Get the new interface documentation and a test environment before the cutover date. If the move is under way, set an approval gate for new customization requests. ## What to check before you decide - Ask the vendor in writing what ends on its date for your current version, and what extended support costs. - Read the contract's clauses on material changes, data access and termination with counsel. - List every customization and integration, and mark each as covered, rebuilt or dropped. - Classify each customization as required by law or contract, by a real operational need, or by habit. - Compare today's full running cost with the subscription plus integrations, over the same period. - Check that your full data history migrates, and how you would export it, in what format and at what cost. - Get a switching quote from one alternative, so you know what refusing the move would cost. ## Questions people ask ### Vendor is ending support for our main system and management proposes a replacement on the vendor's timeline, what should the board check? Check what end of support actually means and when: security fixes, legal changes, extended support options. Then check whether the replacement proposal compared alternatives and whether a staged approach reduces the rush. It depends on what the system does and on the vendor's extended support terms. ### Telematics vendor is forcing a move to their cloud and our integrations will break, what are my options? A vendor-imposed platform change is a contract event, so start with what the agreement says about material changes and data access. Then price the rebuild against switching, including the data history you must keep. It depends on whether your contract lets you refuse the change or exit without penalty. ### Cloud ERP migration under way and the integrator is rebuilding all our old customisations, should I stop that? Yes for most of them, because each rebuilt customisation is a future upgrade cost and usually a process nobody re-examined. Review each one against the standard process and keep only those tied to a real legal, customer or safety need. It depends on how many customisations exist and on whether business owners will accept standard processes. ## How I can help with this decision - **Ask or talk (Free):** I give my view on whether this is a rebuild or a renegotiation, and which clause and which customizations to examine first. - **Review (Pay if it was worth it):** I write an independent assessment of the support situation, the migration's cost, the contract position and the alternatives. I recommend to migrate, renegotiate, stage or leave, and on what timeline. - **Retain (When it makes sense):** I stay close through the migration to review milestones and new customization requests before you approve them. ## Ask me about your case I'll reply personally within two working days with an initial view. [Ask me about your case](https://1pf.co.il/en/#q=Our%20ERP%20vendor%20wants%20us%20on%20their%20cloud%20next%20year.%20How%20do%20we%20decide%20whether%20to%20move%20or%20stay%3F&field=other&src=guide) · [Book 45 minutes](https://1pf.co.il/book/) --- [Decision guides](https://1pf.co.il/en/guides/) · [Home](https://1pf.co.il/en/index.md)