Evaluate, plan, and execute a transition from IBM maintenance to independent support. Covers 50%+ cost savings, extended legacy support, licensing compliance, IBM audit risk, negotiation tactics, and phased transition strategies.
Part of the IBM Knowledge Hub. See also: Decoding IBM Third-Party Support | IBM Licensing Pitfalls | IBM Passport Advantage Guide.
Third-party support means getting product maintenance from an independent provider rather than IBM. You still run your licensed IBM software, but when issues arise, you contact the independent support team. Providers like Origina or Rimini Street specialise in IBM products and offer troubleshooting, bug fixes, technical assistance, and proactive monitoring.
| Characteristic | Detail |
|---|---|
| Independent and vendor-neutral | No push toward upgrades, new licences, or cloud migrations. The provider focuses solely on maintaining your existing systems |
| Legal and legitimate | You choose who supports your software. As long as you remain properly licensed, you have every right to use independent support. It is the car mechanic analogy: certified independent vs dealer |
| Extended legacy support | IBM discontinues support for older releases to push upgrades. Third-party providers fill this gap, supporting legacy versions indefinitely and avoiding forced upgrades |
| High-touch services | Help desk, break/fix, workarounds for known bugs, proactive monitoring, performance tuning, and optimisation advice. Often with dedicated engineers assigned to your account |
| Motivation | Detail |
|---|---|
| Significant cost savings (50%+) | IBM's S&S fees are typically approximately 20% of licence price annually, rising 5-7% per year. Third-party providers charge 50% or more below IBM's standard fees with multi-year price locks. For end-of-life products where IBM charges extended support premiums, savings can reach 70-90%. If you pay IBM $1M/year, a third-party might offer equivalent coverage for $500K |
| Stability: avoid forced upgrades | IBM declares versions end-of-life to push upgrades, forcing businesses onto the vendor's schedule. Third-party support decouples the support lifecycle from IBM's sales-driven upgrade cycle. You stay on a stable, known version as long as it meets your needs |
| Tailored support and flexibility | Dedicated engineers, often ex-IBM experts, assigned to your account with deep familiarity. Custom SLAs with 24/7 coverage, specific response times, tailored terms. Unlike IBM, which may decline support for non-vanilla environments, third-party providers troubleshoot within the context of your specific customisations and integrations |
| Reallocate budget to innovation | By cutting maintenance spend, CIOs redirect funds to digital transformation and growth initiatives. Third-party support acts as a pressure release valve on IT budgets: maintaining reliability through independent support while investing savings in competitive advantages |
Mid-migration systems (why pay full IBM support for software you are retiring?), stable systems with infrequent tickets, legacy products IBM is de-supporting, and environments where you need to buy time before replacement. The ideal candidate is a product where you do not require new features from IBM and plan to run the current version for several more years.
| IBM Product | Why It Is a Good Candidate | Third-Party Support Scope |
|---|---|---|
| Lotus Notes / Domino | Legacy email/collaboration. Older versions no longer receive features. Many organisations have not migrated | User issues, database bugs, security patches for older versions, messaging system maintenance |
| WebSphere | Application Server, Portal, MQ: core middleware running critical apps. Older versions (8.x) stable in production | Multi-version support well past IBM lifecycle. Break/fix, performance tuning, security mitigations |
| Maximo | Enterprise Asset Management: utilities, manufacturing. Older on-prem versions meet needs without IBM cloud push | Bug fixes, usage guidance, custom workflow support, integration assistance |
| Tivoli | IT management/monitoring suite. Many products rebranded or replaced, but legacy versions still mission-critical | Continued support well beyond IBM's window. Monitoring, identity management, storage manager |
| DB2 / Informix | Stable foundational databases. Content with current version, performing well, no need to upgrade | Incident support, performance tuning, compatibility guidance, security patching for older versions |
| Cognos Analytics | BI/reporting suite. Older major versions stable, upgrading is low priority | Report issues, compatibility, BI environment maintenance, security guidance |
| Rational, SPSS, FileNet, Others | Mature products with stable workloads, deep internal expertise, and no need for new vendor features | Version-specific support, known issue resolution, configuration guidance |
| Dimension | IBM Official Support | Third-Party Support |
|---|---|---|
| Annual cost | Approximately 20% of licence price, rising 5-7%/year. Extended support premiums for EOL versions | Typically 50%+ lower with multi-year price locks. No extended support premiums |
| Updates and patches | All official patches, fix packs, security updates, and new version upgrades included | Workarounds, virtual patches, configuration fixes. No new IBM versions |
| Version lifecycle | 3-5 years full support per version. Older versions require expensive extended contracts | Indefinite support for legacy versions. No forced upgrade timeline |
| Responsiveness | Multi-tier escalation (L1 to L2 to L3). Response depends on support level purchased | Direct access to senior engineers. Dedicated account team. Often faster resolution |
| Customisation support | May decline support for non-standard environments | Supports customised environments, integrations, specific configurations |
| Contract flexibility | Annual, auto-renewing, standardised terms. Limited flexibility to reduce scope | Custom SLAs, flexible termination, multi-year locks, scope adjustable to subset of products |
| Vendor incentive | Upsell to new products, cloud services, upgrades | Earn trust through service quality. Customer-centric, no sales pressure |
| Consideration | Detail | Action Required |
|---|---|---|
| Maintain valid perpetual licences | Third-party support does not replace the need for a valid IBM licence. Most traditional IBM software (DB2, WebSphere, Notes) uses perpetual licences that remain valid after support lapses. What you lose is access to upgrades and IBM services, not the right to run the software | Ensure you have documentation: entitlement certificates, Passport Advantage records. Critical: if your licence is subscription-based or term-based, usage rights may expire when you stop renewing. Only drop IBM support for software with perpetual licences |
| No upgrades after leaving support | Without active IBM support, you cannot upgrade to versions released after your support ended. Plan to freeze on a specific version | Upgrade to the latest available version while still under IBM support, then switch. Start the third-party period on the newest codebase you are entitled to |
| IBM can still audit you | IBM retains audit rights regardless of support status. All original licence terms and metrics (PVUs, processors, users) remain in effect. Some industry observers note audit frequency may increase for customers who drop maintenance | Perform an internal licence audit before transitioning using ILMT for sub-capacity. Clean up unneeded installations and true-up any shortfalls while still a paying customer |
| Archive everything before leaving | Once IBM support expires, you lose access to IBM's portal, downloads, and tech notes | Before cancelling: download and archive all software binaries, licence keys, fix packs, release notes, installation files, and documentation you are entitled to |
| Tactic | Detail |
|---|---|
| Leverage third-party quotes | Obtain formal quotes from reputable providers showing 50%+ lower pricing. Present to IBM: this signals a viable alternative. Faced with losing support revenue, IBM may freeze prices, grant unusual discounts, or offer flexible terms they would normally refuse. Either the third-party saves money, or IBM comes back with a much better offer |
| Start early and time strategically | Begin discussions well in advance of your renewal deadline. Communicate concerns about costs and value. Escalate within IBM's hierarchy if needed. Time negotiations to coincide with IBM's fiscal push cycles (end of quarter/year) when they are most motivated to retain revenue |
| Anticipate IBM counter-tactics | FUD (Fear, Uncertainty, Doubt): "Only IBM can fix critical vulnerabilities." Have answers ready: third-party providers employ ex-IBM engineers and develop virtual patches. Relationship appeals: "This will damage the partnership." Reiterate it is a financial decision. Last-minute save offers: one-time discounts that revert to full price, just delaying the decision. Evaluate objectively |
| Handle the formal exit | Formally notify IBM per Passport Advantage terms: written notice by the specific date before anniversary, otherwise support auto-renews. A mixed environment is possible: keep critical products on IBM support while moving others to third-party. Review cross-contract dependencies: bundled discounts on other IBM products might be affected |
IBM reinstatement penalties for lapsed support are typically 150-200% of missed fees, sometimes 3x the annual fee. If you were off support 2 years at $100K/year, reinstatement could cost $200K-$300K+ just to resume. Factor this into your risk calculation. During exit negotiations, ask IBM to waive or cap reinstatement fees as a concession. The cumulative savings from third-party support usually far exceed these penalties, but budget for the scenario.
| Risk Mitigation | Detail |
|---|---|
| Vet the provider thoroughly | Investigate how long they have supported IBM products. Request client references in your industry. Speak to existing customers about responsiveness, expertise, and resolution quality. Check financial stability. Confirm they employ former IBM engineers and have specialists for each product you use |
| Phased transition approach | Avoid overnight cutover for all systems. Start with non-production or less critical systems to test the provider. Stagger by product line across quarters. If a pilot is not possible, ensure a knowledge transfer period where the third party familiarises itself with your environment while IBM support remains active |
| Negotiate strong SLAs | Define response times per severity level (critical = 1 hour response, 4 hours workaround). Include resolution time targets, escalation provisions, regular performance reports, and remedies for SLA breaches (service credits, termination rights). Many providers are amenable to customised SLAs |
| Knowledge transfer and documentation | Share past support tickets and resolutions, system architecture, configuration documents, pending issues, known bugs, and maintenance schedules. Good providers run structured onboarding workshops. Establish an internal owner for the relationship. Define escalation paths |
Research IBM per-incident support (expensive but available). Maintain contact information for independent consultants who could assist in emergencies. Your third-party provider's SLA should minimise these scenarios, but preparation builds stakeholder confidence.
| # | Action | Detail |
|---|---|---|
| 1 | Assess your IBM portfolio | Identify products that are stable, legacy, infrequently updated, or approaching IBM end-of-life. These are your top third-party support candidates. Map each product to its licence type (perpetual vs subscription) |
| 2 | Run an internal compliance audit | Before any transition, verify you are properly licensed for all IBM installations using ILMT. Clean up unneeded deployments. True-up any shortfalls while still a paying customer. This protects against IBM audit risk post-transition |
| 3 | Obtain third-party quotes | Get formal proposals from 2-3 reputable providers. Compare scope, SLAs, pricing, and expertise. Use these quotes as negotiation leverage with IBM even if you have not fully decided to switch |
| 4 | Negotiate with IBM first | Present the alternative and give IBM the chance to match or beat pricing. Start 6+ months before renewal. Escalate if needed. Time discussions around fiscal quarter-ends. Even if IBM does not match fully, you may secure significant concessions |
| 5 | Upgrade to the latest entitled version | While still under IBM support, upgrade to the newest version you are entitled to. This maximises the codebase you start the third-party period with, including latest security patches and features |
| 6 | Archive all IBM resources | Download software binaries, fix packs, licence keys, documentation, and tech notes before cancelling support. You lose portal access after cancellation |
| 7 | Plan a phased transition | Start with non-critical systems. Validate the provider's capabilities before moving mission-critical workloads. Negotiate strong SLAs with escalation provisions and service credit remedies |
| 8 | Designate an internal owner | Assign a vendor manager to monitor the third-party relationship, track SLA performance, and serve as escalation point. Establish internal processes for engaging the new support team |
| 9 | Maintain audit readiness | Even after leaving IBM support, keep licence documentation current. Designate a team member to handle IBM audit requests. Never ignore an audit |
| 10 | Review annually | Reassess whether third-party support still meets your needs. Monitor IBM's product roadmap for must-have innovations. Keep the door open with IBM: the goal is maximising value, not permanent separation |
Yes. You are choosing who supports your software, not changing the software itself. As long as you maintain valid IBM licences (typically perpetual), you have every right to use independent support providers. IBM's support contract covers their services, not your right to run the software.
Typically 50% or more compared to IBM's annual S&S fees. For products at end-of-life where IBM charges extended support premiums, savings can reach 70-90%. Example: $1M/year in IBM support might cost $500K or less through a third-party provider, with multi-year price locks preventing the 5-7% annual escalation IBM typically imposes.
Established, legacy, or highly stable products: Lotus Notes/Domino, WebSphere (Application Server, Portal, MQ), Maximo, Tivoli, DB2, Informix, Cognos, Rational, SPSS, FileNet. The ideal candidate is a product where you do not require new features and plan to run the current version for several more years.
IBM retains audit rights regardless of support status. All licence terms and metrics remain in effect. Perform an internal compliance audit before transitioning using ILMT for sub-capacity, clean up installations, and true-up shortfalls while still a customer. Keep documentation current and designate a team member to handle audit requests.
IBM typically charges 150-200% of missed fees to reinstate lapsed support, sometimes 3x the annual fee in the first year back. If you were off support 2 years at $100K/year, reinstatement could cost $200K-$300K+ just to resume. Factor this into your risk calculation. During exit negotiations, ask IBM to waive or cap reinstatement fees. The cumulative savings usually far exceed these penalties.
Yes. A mixed approach is common. Keep critical products where you anticipate needing upgrades on IBM support. Move stable, legacy systems to third-party. However, IBM historically resists partial support cancellations under bundled agreements. Negotiate separate contracts per product for maximum flexibility. Review cross-contract dependencies to ensure dropping one product's support does not affect discounts on others.
Our independent IBM advisers assess your portfolio, validate compliance, negotiate with IBM, and guide third-party support transitions, delivering consistent cost savings without compliance risk. 100% vendor-independent. Fixed-fee engagement.
IBM Advisory ServicesIndependent IBM advisory. Portfolio assessment. Compliance validation. Negotiation support. Third-party transition guidance. 100% vendor-independent, fixed-fee engagement.