Third-Party Support for IBM Software: The Complete Guide

Third-Party Support for IBM Software – The Complete Guide

Third-party support for IBM software is an alternative maintenance strategy that allows enterprises to reduce costs and gain flexibility by using independent service providers instead of IBM for software support.

This guide provides CIOs and sourcing professionals with a comprehensive overview of third-party IBM support, including its scope, potential benefits and risks, cost considerations, and how it compares to IBM’s support.

It also offers best practices for making the switch. It offers an unbiased, research-based analysis with practical recommendations, a step-by-step checklist, and answers to common questions, all in an authoritative yet accessible format.

Understanding Third-Party Support for IBM Software

Third-party support for IBM software refers to the maintenance and technical support services provided by independent firms, rather than those offered directly by IBM itself.

In practice, it means that after purchasing IBM software licenses, a company can choose to contract a certified external provider to handle updates, troubleshooting, and helpdesk support for those IBM products.

This concept has gained traction as enterprises seek ways to optimize IT budgets.

IBM, like most major software vendors, typically charges high annual maintenance fees (often around 20% of the software’s license price each year) for the privilege of ongoing support and upgrades.

These fees protect vendor profit margins but can consume a large portion of IT budgets. Many organizations have found that a significant share of their annual software spend goes straight into support contracts – money that yields diminishing returns once the software is stable and fully deployed.

How Third-Party Support Works:

With third-party support, companies retain ownership of their IBM software licenses and continue to use the software as usual.

The difference is that they do not renew IBM’s maintenance program (often referred to as IBM Subscription & Support); instead, they pay a third-party provider (often staffed by former IBM engineers or specialists) to provide technical support and maintenance services.

This can include 24/7 helpdesk assistance, troubleshooting of issues, guidance on usage, and even the development of bug fixes or workarounds for problems.

Importantly, third-party providers generally cannot provide new IBM software versions or proprietary patches released after the customer left IBM’s support – these are only legally available through IBM’s official channels.

However, a reputable third-party support firm will assist customers in obtaining any fixes or updates they are still entitled to under their license, and will create custom fixes or mitigation strategies for issues if official patches are not accessible.

Legality and Acceptance: Choosing independent support is entirely legal and within the rights of the software licensee.

IBM’s software licenses allow customers to self-maintain their software or use outside assistance – there is no requirement that support must come directly from IBM.

IBM has never publicly claimed that third-party maintenance is illegal, as doing so could be viewed as anti-competitive.

As long as no intellectual property rights are violated (for example, using only the software versions and patches to which the company is entitled), enterprises are free to seek support from alternative providers.

This practice has already become common among other vendors, such as Oracle and SAP, and now IBM’s customer base is similarly exploring it.

Analyst research indicates that the third-party software support market for major vendors has experienced steady growth in recent years, driven by demand from organizations for lower-cost alternatives.

In the IBM ecosystem, third-party support is still an emerging but maturing option, with a few specialized providers offering services across IBM’s software portfolio.

Why Enterprises Consider Third-Party Support

Global enterprises are turning to third-party support for IBM software primarily to realize significant cost savings and to gain more control over their IT maintenance strategy.

Here are the key benefits and motivations for making this switch:

• Dramatic Cost Savings: The most compelling reason is cost reduction. Companies report saving 50% or more on support fees by moving to third-party providers. IBM’s standard support contracts are expensive – for example, maintaining an IBM software license typically costs about 20% of the license value per year. By contrast, independent support firms often charge roughly half that amount (or even less), thereby immediately reducing maintenance bills. Some enterprises have achieved substantial budget relief; in certain cases, organizations have saved tens of millions over several years or realized overall maintenance cost reductions of 50–90%. These freed-up funds can be redirected to innovation, digital transformation projects, or other strategic IT investments rather than being tied up in routine support costs.
• Extended Product Lifespan (No Forced Upgrades): Third-party support enables businesses to continue using their existing IBM software versions for as long as they meet their business needs, without the pressure to upgrade solely to stay supported. Under IBM’s support policy, products eventually reach End of Support dates, prompting customers to migrate to a newer version or pay for expensive extended support programs. In contrast, an independent support provider will gladly support older or even officially “end-of-life” IBM software releases indefinitely. This means a stable system can continue to run reliably beyond IBM’s support timeline, avoiding disruptive upgrades. Enterprises value this flexibility – if a CRM system or database is working well on, say, IBM Version X, they can stick with it for years longer than IBM might otherwise allow, all while receiving help and fixes from the third-party vendor. The IT team remains in control of upgrade schedules, implementing new versions only when there is a genuine business need, not because of vendor dictates.
• Customized, Responsive Service: Many CIOs and IT leaders also seek a better quality of support service, and third-party providers often differentiate themselves in this area. Whereas large vendors like IBM serve thousands of clients and must prioritize new license sales, a third-party support firm’s entire business is focused on customer support satisfaction. These providers tend to offer more personalized and responsive service – for example, assigning dedicated support engineers to an account, or guaranteeing faster response times for critical issues. Clients frequently find that independent support teams bring deep expertise (often the engineers are former IBM experts with 10-20 years of experience in those specific IBM products) and can often resolve issues more efficiently. There’s also an incentive for the third-party firm to “go the extra mile” to keep the client happy, since support is their core service. In practice, enterprises report positive experiences such as more proactive issue prevention, thorough root-cause analysis on problems, and support staff who are intimately familiar with the client’s environment and customizations. This contrasts with some vendor support experiences where every ticket feels like starting from scratch with a new representative.
• Optimizing IT Spend and Focus: Reducing maintenance costs with third-party support doesn’t just save money; it also helps CIOs rebalance IT spending. Typically, a large portion of the software budget is allocated to “keeping the lights on” through support contracts. By cutting those costs, organizations can free up budget to fund growth initiatives. Additionally, third-party support can sometimes include support for customizations or integrations that vendor support might not cover. The overall effect is that internal IT teams receive more value and assistance in maintaining legacy systems, enabling them to focus more on strategic projects rather than simply administering vendor updates. Some companies also utilize third-party maintenance as a strategic bridge. For example, suppose they plan to eventually replace an IBM application with a different solution (perhaps transitioning to a cloud platform in a few years). In that case, they might employ third-party support in the interim. This way, they avoid pouring money into IBM support for a product with a limited future, while still keeping the system stable until the replacement is ready.

Example:

One CIO of a global consumer goods company publicly shared his rationale for switching to third-party software maintenance, noting that the traditional vendor support model often delivers minimal value in exchange for high fees – essentially just the “right to upgrade.”

This sentiment is echoed by many IT leaders who feel that if their IBM software is stable and not in need of constant updates, paying hefty maintenance fees to IBM yields little benefit.

By contrast, a third-party support agreement focuses on maintaining a stable system that runs smoothly and cost-effectively, without implementing unnecessary upgrades.

Risks and Challenges to Consider

While the benefits are attractive, CIOs must also consider the risks and challenges associated with third-party support for IBM software.

Moving away from IBM’s official support is a significant decision with potential implications.

Key considerations include:

• Strained Vendor Relationship: Choosing an independent support provider can introduce tension in your relationship with IBM. If your company still relies on IBM for other software, hardware, or services, be prepared for your IBM account representatives to push back against any changes. In some cases, vendors have been known to use fear, uncertainty, and doubt (FUD) tactics – emphasizing worst-case scenarios of third-party support – to dissuade customers from leaving their maintenance fold. While many organizations successfully use a mix of vendor and third-party support, it’s wise to communicate your decision to IBM and clarify that it’s driven by cost and service needs. Maintaining a professional relationship is possible, but you should anticipate and manage any pushback. For example, if you’re negotiating new licenses or renewals for other IBM products, be aware that IBM might be less inclined to offer discounts or flexible terms if it sees you reducing spend elsewhere.
• Loss of Upgrade Entitlements: When you opt out of IBM’s support, you give up the entitlement to automatically receive new software versions, patches, and updates from IBM. This means that any IBM software updates released after your support contract expires are not legally accessible to you (unless you resubscribe or negotiate a separate agreement). Third-party support does not restore those entitlements; it works within the scope of the software version you currently have and any updates you have already obtained. The risk is that if a critical new security patch or feature is released exclusively to IBM support customers, your systems could miss out. Reputable third-party providers mitigate this by developing fixes or workarounds for known issues and advising clients to download all available patches before leaving IBM support. Nonetheless, you must be comfortable with the possibility of not receiving future official enhancements. In essence, you are betting that your current software version is sufficient for your needs. If you decide you need an upgrade down the road, you may need to re-enroll in IBM support or purchase new licenses. Both scenarios can be very costly (IBM imposes hefty “reinstatement” fees if you come back after a lapse, often charging back-pay plus a penalty that can amount to several times the normal annual fee). This is why third-party support is best suited for software that is mature in your environment, where feature growth is not a priority.
• Rejoining and Compliance Costs: Another challenge occurs if you ever need to return to IBM’s support. As noted, IBM (like other vendors) typically charges a reinstatement fee for lapsed maintenance. For example, suppose you left IBM support and then decide to resubscribe a year or two later. In that case, IBM may require payment for the missed period plus a surcharge (in some documented cases, returning customers faced fees roughly 160% of the normal annual support cost in the first year back). This can erase the savings you gained from third-party support if not carefully planned. Essentially, the longer you stay on independent support, the more you “earn back” vs. the potential rejoin penalty. Companies should adopt a long-term mindset – third-party support makes the most financial sense when you can commit to it for a multi-year horizon with that software. It’s important to crunch the numbers on break-even points: e.g., if rejoining IBM would cost $X, how many years of third-party savings before you’re ahead? In addition, be mindful of license compliance. Ensure that throughout the third-party support period, you remain compliant with IBM’s licensing rules. Using third-party support is not, in itself, a license violation. Still, you must avoid any usage of IBM intellectual property that you’re not entitled to (like downloading unauthorized patches or having the provider apply code from a newer version you didn’t license). Stick with providers who have clear policies on this – the best providers will refuse to give you any software you aren’t licensed for, which is actually in your best interest legally. There have been cases in the industry (notably with Oracle software) where a third-party support firm engaged in illegal distribution of vendor patches, leading to lawsuits. You do not want your organization caught in such a scenario.
• Quality and Scope of Support: The level of service from a third-party provider can vary, and there is a risk that it might not meet expectations or match what IBM could offer in certain areas. For example, IBM’s support has direct access to the product development teams and source code – in theory, they can issue official patches or hotfixes for complex software bugs. An independent provider does not have that direct pipeline; instead, they rely on their engineers’ expertise to troubleshoot and craft solutions. In many cases, this approach works well, especially for known issues or common configurations. However, for very obscure or deeply embedded software flaws, a third-party might have limitations. It’s essential to assess whether the provider possesses the necessary technical expertise for your IBM products. Ask: Do they have specialists for IBM WebSphere if that’s your product? How will they handle a severe production issue in the IBM Db2 database? What if a new regulatory change (say, updated tax calculation rules in IBM software) is needed – can they help, or would IBM’s update be required? Generally, strong third-party vendors have good answers to these questions (often they build their patches or provide advisory support to configure workarounds). Nonetheless, doing due diligence is crucial. Also, consider the support scope: IBM’s contracts may include certain extras, such as access to knowledge bases or compatibility assessments for new platforms – make sure you won’t lose any critical resources when switching.
• Not for Every Situation: It’s worth noting that third-party support is not a one-size-fits-all solution. There are scenarios where staying with IBM makes more sense. For instance, if an IBM software product is still in active deployment or undergoing heavy development in your environment, or if your business strategy relies on adopting new features as they become available, then the vendor’s support (with continuous upgrades) might be invaluable. Early in a product’s lifecycle or during a major version migration, having IBM’s official backing could reduce risk. Many organizations therefore adopt a hybrid approach – they use third-party support for older, stable systems that are essentially in maintenance mode, but keep vendor support for cutting-edge or mission-critical applications that are evolving. This selective strategy can optimize costs while managing risk. The key is to carefully identify which systems are good candidates; typically, these are those that are stable, well-understood by your team, and not expected to require major updates. In those areas, the risks can be managed, and the cost savings are very attractive.

In summary, due diligence and strategic planning are essential. The challenges of third-party support for IBM software can be addressed through proper planning. To mitigate relationship issues, maintain open communication with IBM.

Ensure you fully understand your license entitlements before switching. Additionally, vet your third-party provider’s capabilities and integrity.

With these precautions, many enterprises have successfully navigated the transition and reaped substantial benefits.

IBM vs. Third-Party Support: Key Differences

How does third-party support for IBM software compare to IBM’s support offerings?

The following table summarizes the key differences across several dimensions that matter to enterprises:

As shown above, the trade-off essentially comes down to cost vs. direct vendor involvement. IBM’s support guarantees that you are always on the latest updates, backed by the vendor’s official support, which can be important for certain products.

Third-party support prioritizes cost efficiency, independence, and life extension of existing systems, at the cost of losing automatic access to future IBM releases.

Many enterprises decide on a case-by-case basis: for stable, mature systems (where new updates provide little value), third-party support often prevails; for rapidly evolving or highly strategic platforms, they might opt to stick with IBM.

It’s also possible to mix models – for example, an organization might use IBM support for a cutting-edge analytics platform but use third-party support for legacy IBM middleware that they intend to phase out in a few years.

The key is aligning the support model with the business needs of each system.

Choosing the Right Third-Party Support Provider

If you decide to explore third-party support for IBM software, selecting the right provider is critical. This market, while growing, is relatively specialized, and the quality of service can vary significantly between providers.

Here’s how to approach the selection:

• Know the Key Players: There are a handful of well-known third-party support providers that service IBM software. Notably, Origina is a specialist firm focused specifically on IBM software support (covering products like IBM WebSphere, Db2, Tivoli, Cognos, and many others). Rimini Street, one of the largest third-party support companies (famous for its support of Oracle and SAP), also offers IBM software support as part of its portfolio, boasting global coverage. Spinnaker Support is another established vendor that covers IBM, as well as other enterprise software maintenance. These companies have built reputations in the industry and are often mentioned in analyst reports.
  Additionally, there may be smaller regional or product-specific providers, depending on the specific IBM software in question. For example, some niche firms might focus on IBM mainframe software support, or on former IBM products now sold to HCL. While the third-party support market for IBM is not as crowded as that for Oracle or SAP, it’s mature enough that you can find a provider with the right expertise for most IBM software products.
• Evaluate Experience and Expertise: Look for a provider with a proven track record supporting the specific IBM software your enterprise relies on. Ask potential providers for case studies or references where they have maintained the same IBM product (for example, if you need support for IBM Maximo or IBM Informix, ensure the provider has expert engineers for those systems). The depth of expertise is crucial – the provider’s team should include former IBM professionals or seasoned experts who thoroughly understand the product’s intricacies. During the evaluation, inquire about their staffing: Do they have dedicated specialists for databases, middleware, business analytics, and other relevant areas? How many clients do they support on the IBM product version you use? The goal is to gauge whether they can truly handle your environment.
• Service Offerings and SLA: Differentiate providers by the services they offer and their corresponding service level agreements (SLAs). Nearly all will claim 24×7 support, but dig deeper. What is the guaranteed response time for critical issues? Will you have a named support engineer or team familiar with your account? Do they offer proactive services, such as health checks, performance tuning, or security vulnerability monitoring, for your IBM software? Consider what you currently get from IBM and what you wish you could get – then see if the third-party can meet or exceed that. A top provider will often have a more customer-centric approach, such as flexible support models (perhaps unlimited support incidents or support for custom code at no extra cost) that contrast with IBM’s often standard tiered support. Ensure the provider’s proposed SLA aligns with your business requirements, especially for any high-availability systems.
• Check References and Reputation: Treat this like any critical outsourcing decision. Ask each shortlisted provider to supply multiple customer references – ideally, enterprises of a similar size and in a similar industry that use the same IBM software. Then actually speak to those references. This will give you insight into the real-world performance of the provider: Are they meeting their promises? How is their responsiveness in practice? Do they truly solve issues without trying to upsell something else? Additionally, research the provider’s reputation. Independent reviews, Gartner or other analyst peer reviews, and industry forums (like IT asset management or user groups) can shed light on strengths and any weaknesses. You want to ensure the company is stable (both financially and operationally), as you intend to rely on them for years. The last thing you need is a provider that goes out of business or becomes unreliable. Fortunately, the leading third-party support firms for IBM have been in operation for several years and have established.
  Growing client bases is a positive sign.
• Contract and Flexibility: When you move to third-party support, you will be signing a contract that defines exactly what they will do. Scrutinize these terms. Pay attention to how the provider handles liability if an issue isn’t resolved, and what remedies exist (while major incidents are rare, you need clarity on responsibilities). Ensure there are provisions about intellectual property compliance – the contract should stipulate that the provider will not introduce any unlicensed IBM code or patches, protecting you from legal risk. Also, clarify the process if you choose to end the contract: Will they assist in knowledge transfer, and how far in advance do you need to notify them? A customer-friendly contract may allow for annual renewals without a long-term lock-in (although many offer discounts for multi-year commitments). Flexibility is often a selling point of third-party providers, so don’t be afraid to negotiate terms that matter to you, such as support for specific in-house modifications or inclusion of minor upgrades you already have rights to.
• Pilot and Transition Plan: Finally, plan the transition carefully. Align the switch with the expiration of your IBM support contract to avoid any coverage gap (many companies time it so that the third-party coverage starts immediately after IBM support ends). It’s advisable to have all the necessary IBM downloads (documentation, final patches, etc.) from your customer portal before the cut-off date. Some organizations conduct a “test run” by engaging the third-party provider in a limited capacity before fully transitioning – for example, during contract negotiations, you might ask them to perform an assessment or handle a non-critical support query to gauge their performance. While not always possible, this can increase confidence. At a minimum, ensure that your team and the provider conduct a thorough onboarding process, sharing system documentation, incident history, and any known problem areas so that the provider is up to speed from day one. A well-prepared transition often results in end users not even noticing that the support provider has changed – except perhaps for faster resolution times.

By taking these steps, you can select a third-party support provider that fits your enterprise’s needs and set the stage for a successful partnership.

The goal is to achieve the promised savings and service improvements with minimal disruption.

When done right, third-party support for IBM software can become a stable, long-term solution in your IT strategy, delivering the best of both worlds: reliable support and freed-up resources for innovation.

Recommendations

For organizations considering third-party support for IBM software, here are expert tips and best practices to ensure success:

• 1. Identify Ideal Candidates: Start by pinpointing which IBM software systems are best suited for third-party support. Look for mature, stable applications that are critical but not undergoing frequent changes. If a system has been running reliably and you don’t anticipate needing major upgrades, it’s a good candidate. By contrast, if an application is in active development or you rely on upcoming IBM enhancements, keep that under IBM support for now.
• 2. Calculate the Business Case: Do a thorough cost-benefit analysis. Calculate your current annual IBM support spend on the target software and compare it to quotes from third-party providers (which might be half the cost or less). Factor in any one-time switching costs. Also, consider the cost of not getting new upgrades – is that acceptable? If the software meets needs in its current state for 3-5 years, the savings over that period will likely far outweigh any future rejoining costs. Present this business case clearly to executives, highlighting potential savings that can be reallocated to strategic projects.
• 3. Secure Internal Buy-In: Involve all stakeholders early. Get support from IT operations teams (who will work directly with the new provider) and from procurement and finance (who will want to validate the savings and contractual terms). It’s also wise to brief your legal team so they are comfortable that license compliance will be maintained. By building a coalition internally, you ensure that the decision is understood and supported across the organization, which will help if there’s any pushback from the vendor or concerns that need to be addressed.
• 4. Engage in Due Diligence: Treat selecting a third-party support firm with the same rigor as selecting any critical service provider. Develop a checklist of questions covering their experience with your specific IBM products, the qualifications of their support staff, references from similar clients, and their processes for handling issues. Evaluate multiple providers if possible. Be wary of any provider that promises something “too good to be true” (such as providing IBM’s proprietary updates illegally). A trustworthy partner will be honest about limitations and focus on how they add value through their expertise.
• 5. Plan the Transition Meticulously: Once you choose a provider, work jointly to create a solid transition plan. Document all your current support cases, known issues, and environment details to bring the new team up to speed. Schedule knowledge transfer sessions if needed. Ensure there’s no gap between when IBM support ends and the third-party begins – align contract dates carefully. Download any last patches or documentation from IBM’s portal while you still have access. Communicate the new support process and contacts to your IT staff (and possibly end-users). A smooth handover is crucial to preventing any service disruptions.
• 6. Maintain Vendor Relationships: Even after switching, keep communication channels open with IBM if you continue to use other IBM products. There’s no need for an adversarial stance. You can inform your IBM account manager of your decision and the reasons (focus on cost and specific needs). Reinforce that you remain a valued IBM customer in other areas. This transparency can help mitigate any negative impacts and preserve goodwill for future interactions or if you ever need to license additional software. Many companies manage this diplomatically – for example, by continuing to attend IBM user groups or briefings, but not purchasing support for that particular product.
• 7. Monitor and Review Performance: After transitioning, continuously monitor the third-party provider’s performance against SLAs and expectations. Track metrics like response times, issue resolution quality, and any trends in system stability. Schedule quarterly service reviews with the provider to discuss what’s working and any areas for improvement. By keeping a close eye, you can ensure you’re getting the value promised. If any issues arise, address them early with the provider. Most will be eager to resolve concerns to keep your business. Regular reviews also help you capture the benefits (e.g., quantifying the cost saved, improvements in support satisfaction), which you can report back to stakeholders.
• 8. Have an Exit Strategy: While the goal is a successful long-term relationship, always have a contingency plan. Understand what it would involve if circumstances changed – for instance, if a new business need required upgrading to the latest IBM version in the future, how would you handle that? Being prepared may involve knowing the process and cost of re-enrolling in IBM support or purchasing new licenses if necessary. Similarly, ensure your contract with the provider allows you to gracefully exit if needed (with appropriate notice). Having this foresight doesn’t mean you will abandon third-party support, but it ensures you’re never stuck without options.

Checklist: 5 Actions to Take

If you’re ready to proceed with third-party support for IBM software, use this simple checklist to guide your action plan:

1. Inventory and Assess Your IBM Software: Make a list of all IBM software products in use. Identify which ones are stable and suitable for third-party support. Note current versions, support end dates, and any upcoming projects or dependencies for each system. This will clarify the candidates for independent support.
2. Gather Data and Requirements: Calculate how much you’re paying for IBM support on the target systems and note the service levels you receive. Additionally, outline your support requirements (e.g., 24/7 coverage, specific response times for severity-1 issues, support for custom modifications, etc.). Having these requirements documented will help in discussions with potential providers.
3. Research Providers and Request Proposals: Reach out to reputable third-party support vendors that specialize in IBM software. Provide them with a high-level overview of your environment (types of IBM software, number of licenses, locations, etc.) and request a proposal or quote. Evaluate at least two providers, if possible. Use an RFP (Request for Proposal) process to ask detailed questions about their services, experience, security practices, and pricing. Comparing proposals side by side will make the decision clearer.
4. Evaluate and Select the Provider: Organize meetings or workshops with the top provider candidates to assess their suitability. Include your technical teams to ask questions about how issues would be handled. Check references by talking to existing customers of the providers. Score each provider on factors like cost savings, expertise, SLA, and cultural fit with your organization. Then select the provider that best meets your needs and offers confidence in their ability to support your IBM environment effectively.
5. Plan and Execute the Switch: Collaborate with the chosen provider to develop a comprehensive transition project plan. Key tasks should include: notifying IBM of non-renewal (if required by contract), signing the new support agreement, conducting orientation sessions with the provider’s support team, setting up support contacts and escalation paths, and scheduling the official cutover date. Execute the plan during a low-risk period if possible (not during a critical business peak). After the switch, closely monitor the support process and gather feedback from your IT staff to ensure everything is running smoothly. Celebrate the cost savings and communicate the success internally, as this builds confidence in pursuing similar optimization initiatives.

FAQs

Q1: Is it legal and acceptable to use third-party support for IBM software?
A: Yes. It is both legal and a fairly common practice in the enterprise software world. When you purchase an IBM software license, you have the right to maintain and service that software yourself or via any third party you choose. There are no license terms requiring you to buy IBM’s support. Many organizations, including large enterprises, use third-party support for IBM and other vendors’ software to save costs. The key is to stay within your license rights (for example, only using software versions and patches to which you’re entitled). Reputable third-party providers respect these boundaries. IBM might not love the idea of you leaving their support, but they cannot void your license or penalize you as long as you comply with the contract. Independent support has grown significantly, to the point where industry analysts now openly recommend it as a viable option to consider.

Q2: What do we lose by not having IBM’s official support?
A: The main thing you relinquish is access to any new IBM software releases, patches, and direct vendor resources beyond the date you leave IBM support. You will no longer be able to download new fix packs or upgrade to new major versions as part of a support entitlement. Additionally, you won’t have IBM’s support team to escalate issues to – meaning if there’s a deeply technical bug, IBM’s engineers won’t be on call to assist. However, a good third-party provider steps in to fill the gap for day-to-day problem resolution and can often create fixes for bugs or guide workarounds. Many companies find that for a stable software version, they don’t need the vendor’s new patches very often (or those patches can be obtained through alternative means if they are critical). You should also consider that IBM’s support sometimes includes other perks, such as access to online knowledge bases or forums – typically, these remain accessible only to active support customers. In short, you trade away future updates and direct vendor support, but you retain the ability to use your current software fully, with another expert team providing support.

Q3: How much money can we save with third-party support?
A: Organizations generally save at least 50% on annual support fees for the targeted software, and sometimes more. If you’re paying $1 million a year to IBM for a certain software’s maintenance, a third-party might charge around $500,000 (or even less in some cases). Those savings accumulate year over year. Beyond the contract fee reduction, there are indirect savings too: you avoid costly forced upgrades (which themselves can run into millions in project costs for new hardware, migration effort, retraining, etc., just to stay supported). By deferring or eliminating those upgrades, the total cost benefit can be very large. Some companies have reported saving tens of percent of their overall IT budget by smartly leveraging third-party support on multiple software systems. That said, it’s important to quantify it for your specific case. The exact savings will depend on IBM’s pricing for your product and the third party’s quote. But typically, expect roughly half off your maintenance costs as a baseline. Over five years, that could translate into millions saved for a large enterprise, which is why CIOs find this so attractive.

Q4: How do third-party providers handle critical patches and security updates if we’re not getting those from IBM?
A: This is a very important question. Top third-party support providers have methodologies to keep your systems secure and up-to-date even without direct vendor patches. They monitor known vulnerabilities and industry updates. If IBM releases a security patch for a newly discovered vulnerability, a third-party provider cannot give you that exact patch if it was released after your support ended (that would violate license terms). However, they will typically do one of two things: either help you implement a functionally similar fix (for example, tweaking the configuration or applying an open-source security fix, if applicable), or they will backport a solution from scratch. Many providers employ security specialists who can develop custom code fixes or mitigate vulnerabilities by other means (such as firewall rules or disabling a vulnerable component, etc.). For compliance updates (such as tax or regulatory changes in software), they will similarly create patches or provide updated configurations to ensure you remain compliant. Essentially, the third-party becomes your “fixer” for any issue – if something needs patching, they take on the responsibility to address it, just as IBM would have. It’s wise to discuss this process with any prospective provider: ask for examples of how they delivered a security update or kept a client compliant without official vendor patches. You’ll find that the reputable firms have well-defined processes for this scenario. In many cases, you might even get faster attention on critical issues from a third party, because your business isn’t one of thousands in a queue.

Q5: Can we switch back to IBM’s support in the future if we choose to?
A: Yes, you can return to IBM support in the future, but it may come at a cost. IBM (like most vendors) will welcome you back as a customer, but typically requires you to pay for the period you were not under support (or purchase new licenses). This is known as a maintenance reinstatement fee. For example, if you left IBM support for two years, IBM might ask for those two years of fees plus a penalty to reinstate support on your existing licenses. This can be expensive – sometimes a few times the normal annual fee upfront. Another approach is to purchase the software afresh, which is usually impractical unless the software cost is low. The possibility of switching back exists if your circumstances change (for instance, if a new version proves so beneficial that you decide to upgrade), but you should plan carefully. If there’s a chance you’ll need to return to IBM support soon, the financial case for third-party support weakens. Ideally, you adopt third-party support with a multi-year horizon in mind. Many companies continue to rely on independent support for the remainder of the software’s life in their organization. However, if you do need IBM again in the future, make sure to factor in the re-entry cost. Some companies negotiated with IBM at that time – occasionally, IBM might offer a deal to incentivize them back. In any event, it’s not a point of no return; it’s just something that requires budgeting if it happens. A good strategy is to periodically re-evaluate your decision (say, annually): if your needs haven’t changed, you stay the course with the third-party; if your strategy shifts (like deciding to upgrade or expand usage), you can then consider re-engaging IBM with full knowledge of the cost implications.

Do you want to know more about IBM Third Party Support?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit