SAP GTS 11 End of Maintenance: What Trade Compliance Teams Must Do Now After the December 2025 Deadline

What SAP GTS 11 Does (and Why It Matters)

SAP Global Trade Services (GTS) is a specialized module that sits inside SAP ECC or runs as a standalone application. It handles the mechanics of international trade compliance: managing tariff classifications, calculating duty obligations, screening shipments against sanctions lists, enforcing export controls, managing embargo regulations, and generating the documentation required for customs clearance.

For enterprises with significant international operations—manufacturing, logistics, automotive, pharmaceuticals, chemicals, electronics—GTS isn't optional. It's the system of record for trade compliance. If it fails, shipments stop. If it produces incorrect calculations, you face tariff penalties. If it doesn't screen against OFAC or EU sanctions lists correctly, you face criminal liability.

What GTS 11 Handles

• Duty Calculation: Automated tariff classification and duty amount computation based on product, origin, and destination rules
• Sanctions Screening: Real-time screening against OFAC, EU, UK, UN sanctions lists; prevents shipments to blocked parties
• Export Controls: Enforces ITAR, EAR, and other export control regulations on sensitive materials and technology
• Embargo Management: Prevents shipments to embargoed countries (Iran, North Korea, Syria, Crimea, etc.)
• Rules of Origin: Applies FTA and preferential trade rules to minimize duty costs
• Customs Documentation: Generates invoices, packing lists, certificates of origin, and customs declarations
• Landed Cost: Computes total cost of goods including duties, taxes, insurance, and freight for cost accounting

In regulated industries like pharmaceuticals, defense, aerospace, and export-sensitive chemicals, running outdated GTS software creates a paper trail showing management knew the system was unsupported when violations occurred. Regulators view this as negligence.

The December 2025 Mainstream Maintenance Deadline

SAP announced the end of mainstream support for GTS 11 on December 31, 2025. This date passed. "Mainstream maintenance" means SAP will no longer issue:

• Bug fixes
• Security patches
• Performance updates
• Regulatory compliance updates (new sanctions lists, export control changes)

The practical implication: if a security vulnerability is discovered in GTS 11 after December 2025, SAP will not patch it. If new sanctions regulations are announced, GTS 11 cannot be updated to comply. If the system crashes, SAP will direct you to upgrade rather than fix the issue.

For trade compliance teams, this is especially dangerous because sanctions lists, export control regulations, and tariff classifications change frequently. A trade compliance system that cannot be patched for regulatory changes is not a system—it's technical debt masquerading as infrastructure.

Maintenance Types: Mainstream vs Extended vs Customer-Specific

SAP uses a tiered support model designed to trap customers with high switching costs. Understanding these tiers is essential for negotiating your migration path.

Mainstream Maintenance (Now Expired)

This is what GTS 11 had until December 31, 2025. It included unlimited bug fixes, security patches, and updates for no additional fee (beyond your annual support subscription). The standard support cost is roughly 22% of the license list price annually.

Extended Maintenance (SAP's Trap)

After mainstream maintenance ends, SAP offers extended support. The pitch is simple: stay on GTS 11 without upgrading, pay an annual fee. The reality is expensive:

• Cost: 25-30% of license list price per year (higher than mainstream)
• Duration: Typically offered for 3-5 years post-mainstream end, or until 2030-2032 for GTS 11
• Total Cost: A mid-market company with 50-100 GTS users could spend $300,000-$500,000+ for extended support over 3-5 years
• What's Included: Reactive bug fixes ONLY. You request a fix, SAP evaluates if it's worth fixing for an old release. No proactive updates, no regulatory enhancements

Extended maintenance is designed to make migration look cheaper than staying put. For organizations with 200+ GTS users, extended maintenance can exceed $1M over five years.

Customer-Specific Maintenance (The Hidden Fee)

If your organization is strategically important to SAP (large enterprise, extended contract, high ARR), SAP may offer customer-specific support at negotiated rates. This is a mythical tier—it's not published, only offered to specific accounts as a retention tactic.

Costs typically fall between extended maintenance and a new license. The catch: you're locked into an even longer contract with SAP, with annual escalation clauses (3-5% annually typical).

The Math for Your Organization

Before accepting extended maintenance, calculate the total cost to stay on GTS 11 for 3-5 more years, add the eventual migration cost when extended support ends, and compare to migrating now. Most organizations find that paying migration costs now is cheaper than extended support fees plus eventual migration fees.

Four Migration Paths and Their Real Costs

SAP has four primary paths for organizations running GTS 11. Each has different technical, licensing, and cost implications. Each also has different compliance and operational footprints.

Option 1: SAP GTS Embedded in S/4HANA

The standard SAP recommendation: migrate your entire ERP to S/4HANA and run GTS as an embedded module. This is the simplest from an SAP perspective (one ERP, one database, one support contract) but the most disruptive to execute.

• Licensing: GTS is licensed as a function within S/4HANA. No separate GTS license. Instead, you pay for S/4HANA core modules (Finance, Procurement, Logistics) plus mandatory GTS functionality.
• Typical Costs: S/4HANA licenses at $15,000-$25,000 per user (depending on edition). A 100-user implementation could cost $1.5M-$2.5M in licenses alone, plus implementation costs of $2M-$5M+ for large organizations.
• Implementation Timeline: 18-36 months for most organizations
• Risk: Full ERP migration. If your ECC system is stable and working, you're paying to migrate it. This is often justified to SAP as "consolidation" and "modernization," but the primary driver is usually just moving off old versions.

When to Choose This: If you're already planning an S/4HANA migration for other reasons (end of ECC support in 2027, business transformation), bundling GTS 11 migration into that program makes sense. Standalone for GTS 11? Rarely justified.

Option 2: SAP Logistics Business Network (LBN)

SAP's cloud-native alternative to GTS. It's positioned as a "Supply Chain Network" that sits between your ERP and partners/customs brokers. LBN handles trade compliance, logistics orchestration, and shipment visibility.

• Licensing Model: Subscription-based SaaS. Price per shipment, per month, or per transaction. Typically $50,000-$150,000 annually depending on transaction volume.
• Implementation: Faster than S/4HANA migration (6-12 months). Lighter touch on your core ERP.
• Advantage: Cloud-native, automatically updated, includes latest regulatory data, integrates with customs brokers and trading partners.
• Disadvantage: Separate system from your ERP. Data must be synchronized. Trade compliance logic now lives in the cloud, not in your ECC/S/4HANA system of record. More complex data governance.

When to Choose This: If you have complex supply chains with multiple trading partners, use customs brokers heavily, or need to reduce on-premise infrastructure. Best for organizations with 50+ users or high transaction volume.

Option 3: SAP GTS in RISE with SAP

RISE is SAP's managed cloud offering: you get S/4HANA, SAP Analytics Cloud, embedded GTS, and SAP's managed services all as a single monthly subscription. It's SAP's push toward outcome-based contracts rather than license-based.

• Licensing: No traditional licenses. Instead, subscription fees based on users, transactions, and cloud resources. Typically $200,000-$500,000+ annually for mid-market.
• Implementation: SAP delivers the infrastructure, but your organization still executes the GTS configuration and cutover. 12-24 months typical.
• Support: Included in subscription. All patches, updates, and regulatory changes are automatically deployed.
• Advantage: Predictable costs (no surprise support bills), always current on compliance, SAP manages infrastructure.
• Disadvantage: Vendor lock-in. You're renting infrastructure and software from SAP with no exit clause. Annual price increases typical. After 5-10 years, total cost of ownership can exceed traditional licensing.

When to Choose This: If you want predictable costs, prefer SaaS, and accept vendor lock-in. RISE works well for organizations that don't want to manage on-premise infrastructure.

Option 4: Non-SAP Trade Compliance Solutions

The option SAP doesn't want you to consider: replace GTS with a specialized trade compliance platform. Vendors like Amber Road (now Flexport), Thomson Reuters ONESOURCE Trade Compliance, or Intra (acquired by Descartes Systems) focus exclusively on trade compliance and often provide better UX, faster updates, and more flexible pricing.

• Licensing: Typically SaaS subscription. $50,000-$200,000 annually depending on features and transaction volume.
• Implementation: 6-12 months. Can run parallel to GTS during transition.
• Advantage: Best-of-breed for trade compliance. Better regulatory update frequency. Not locked into SAP's release cycle.
• Disadvantage: Separate from your ERP. Data synchronization required. Your trade team uses one system, your finance/procurement teams use another.
• SAP's Resistance: SAP will argue this adds complexity. They're not wrong—but they're also defending their revenue stream.

When to Choose This: If your trade compliance function is sophisticated and you want specialized best-of-breed tools. Best for organizations with dedicated trade teams and complex compliance requirements.

Migration Options Comparison

Licensing Implications by Migration Path

This is where SAP makes its money, and where most organizations overpay. The licensing model changes depending on your migration path, and SAP's sales process is designed to maximize license count and feature modules.

GTS 11 Standalone Licensing (Current State)

If you're running GTS 11 today as a standalone system or embedded in ECC, your licensing is straightforward:

• Named User Licenses: One license per person who uses GTS. Typically $4,000-$8,000 per user, depending on ECC version and negotiated discounts.
• Annual Support: 22% of license list price per year.
• Example: 80 GTS users at $6,000 per license = $480,000 license cost. Annual support = $105,600.

This is manageable and hasn't changed since GTS 11 launched. The problem: it can't stay this way indefinitely.

S/4HANA GTS Licensing (The Hidden Bloat)

When you migrate GTS into S/4HANA, the licensing model changes completely. You're no longer buying "GTS licenses"—you're buying S/4HANA core licenses, which are expensive, plus mandatory feature modules.

• S/4HANA Core License: $20,000-$30,000 per user for full functionality
• Trade Management Module: Included in core (non-negotiable)
• Example: 100 users on S/4HANA at $25,000 per license = $2,500,000 in license cost
• Support: 22% annually = $550,000 per year

This is why SAP pushes S/4HANA migration: licensing revenue increases 4-5x. Your organization goes from $480K in GTS licenses to $2.5M in S/4HANA licenses. The "business case" for migration often fails when you isolate the licensing multiplier.

LBN and Non-SAP Platform Licensing (The Escape Hatch)

Subscription-based SaaS platforms charge per transaction, user, or month. They don't have the licensing complexity SAP uses.

• Amber Road (Flexport): $100K-$300K annually depending on shipment volume
• LBN: $75K-$200K annually depending on transaction volume
• No surprise fees, no per-user multipliers, no hidden modules

From SAP's perspective, these are threats because they replace license-driven revenue with simpler subscription models.

RISE with SAP Licensing (The Monthly Trap)

RISE converts license costs into subscription fees, which SAP claims is more "flexible." In reality:

• Cloud Infrastructure: You pay for compute/storage monthly (variable)
• Software Subscription: Fixed monthly fee based on user count and transaction volume
• Example: 100 users + moderate transaction volume = $250,000-$400,000 annually. After 5 years: $1.25M-$2M
• Annual Price Increases: Typical 3-5% annually (compounding)

RISE sounds like it eliminates the license burden, but over 10 years, you'll pay more in subscription fees than you would have in traditional license + support. The lock-in is deeper because you can't run your own infrastructure—you're entirely dependent on SAP's cloud.

Audit and Compliance Risk: The Regulatory Angle

Running unsupported trade compliance software is not just a technical problem—it's a compliance and audit liability. Regulators and auditors now track software end-of-life status.

Who Cares That GTS 11 Is Unsupported?

• OFAC and Bureau of Industry & Security (BIS): Export enforcement agencies. If you ship a controlled item to a sanctioned entity and your compliance system is unsupported, OFAC views this as negligent screening. Penalties can exceed $100,000 per violation, multiplied by transaction count.
• U.S. Customs and Border Protection (CBP): The agency that audits trade compliance programs. An unsupported trade system is a red flag for audit severity.
• EU Customs Authorities: If you have European operations, the same logic applies. Running outdated export control systems creates liability in GDPR-regulated environments.
• Internal Audit and Compliance Teams: These teams are now tracking software lifecycle management and flagging unsupported systems as control weaknesses.
• External Auditors (Big 4 and equivalents): When auditing your internal controls, they look for reliance on unsupported systems as a material weakness.

The Regulatory Exposure

Consider this scenario: your organization exports dual-use goods (items that have both commercial and military applications). Your GTS 11 system fails to screen against a new OFAC designation because SAP hasn't patched it (and won't, since it's unsupported). You ship to a sanctioned entity, unknowingly. Six months later, OFAC audits your exports.

OFAC's auditors ask: "When did SAP end support for GTS 11?" December 2025. "When did you migrate?" Still running it. "Did you know the system was unsupported?" You likely have email evidence that you did.

You've now moved from "failure to comply" to "knowing failure to comply"—a negligence case. Penalties escalate. Criminal referrals become more likely.

How to Protect Yourself

• Document the Decision: Create a memo documenting that GTS 11 reached end of maintenance and that your organization made an active decision to remain on the system (either through extended maintenance or while planning migration).
• Define the Control Compensating for the Risk: If you're staying on GTS 11 for more than 90 days post-December 2025, implement a compensating control (manual secondary screening, third-party compliance review) that mitigates the risk of an outdated system.
• Accelerate Migration: The best long-term defense is migration. Every month you remain on unsupported GTS 11 increases regulatory exposure. Regulators understand the difference between "migrating off an unsupported system" and "running an unsupported system indefinitely."

Negotiation Strategy: Using This Deadline to Your Advantage

The December 2025 GTS 11 end-of-life creates a negotiation opportunity. SAP wants you to migrate to a higher-revenue product. You can use this to extract concessions on licensing, support costs, and contract terms.

The Negotiation Playbook

Step 1: Don't Accept Extended Maintenance (The Trap)

When SAP offers extended maintenance for GTS 11, refuse it immediately. Extended maintenance is expensive ($200K-$500K+ over 3-5 years) and delays decision-making. By staying on extended maintenance, you're paying SAP to delay your migration, which maximizes SAP's negotiating position. Instead, force SAP to make a proposal for migration.

Step 2: Request a Total Cost of Ownership (TCO) Comparison

Demand that SAP provide a formal TCO for all four migration options:

• Extended maintenance for GTS 11 (5 years + eventual migration)
• GTS embedded in S/4HANA
• LBN
• RISE with SAP

SAP will provide this, but their TCO will be biased toward S/4HANA migration. When they do, have your own independent consultant (like us) review it. SAP often:

• Underestimates implementation costs for their preferred option
• Overestimates costs for alternatives
• Uses best-case timelines for S/4HANA (18 months) that rarely happen (36+ months is common)
• Excludes post-go-live support costs in the TCO

Step 3: Use the Deadline to Create Urgency (On Your Side)

Tell your SAP Account Executive: "We need to make a decision by Q2 2026 (or another deadline of your choice). If you can't provide a compelling business case for migration by then, we'll either extend on GTS 11 or evaluate non-SAP alternatives."

This creates real pressure on SAP. They know that the longer they wait, the more likely you'll explore Amber Road, Descartes, or Thomson Reuters alternatives. SAP will then negotiate harder on pricing and terms to keep you in the SAP ecosystem.

Step 4: Negotiate on License Count and Edition

When migrating to S/4HANA, SAP will push for licenses for everyone who "touches" the system. Resist. Negotiate:

• Named User counts: Don't accept SAP's proposed user count. Demand a detailed usage audit. Often, SAP's recommendations include 20-30% more users than actually needed.
• Edition: Ensure you're not forced into a higher-tier edition. If you're a mid-market company, Enterprise Edition may be overkill. Sometimes SAP will force Enterprise Edition when Standard Edition meets your needs.
• Optional Modules: Don't accept mandatory modules you won't use. If GTS is your primary need, don't pay extra for Advanced Planning or other modules you don't need.

Step 5: Negotiate Support Costs

Standard support is 22% of license list price. For large deals, negotiate this down to 18-20%. This might seem small, but on a $2M license cost, this saves $40K-$80K annually and compounds over years.

Step 6: Demand a Fixed-Price Implementation (Or Manage the Scope)

Don't accept a T&M (time and materials) implementation contract. SAP's partners will burn through 30,000+ hours if you let them. Demand a fixed-price implementation with clear scope boundaries. If that's not possible, cap the T&M hours and require monthly accounting of hours consumed.

Step 7: Structure the Contract to Enable an Exit (Or At Least Raise Its Cost)

Negotiate contract terms that allow you to exit or reduce licenses if the implementation goes sideways. Ensure you have:

• A sunset clause if the system doesn't reach production within an agreed timeframe
• The right to reduce named users after go-live if actual usage is lower than forecasted
• Clear metrics for what "success" looks like and the right to renegotiate if those metrics aren't met

Our contract negotiation service focuses on these exact scenarios. We review SAP's proposals, identify overreach, and negotiate more favorable terms on your behalf.

90-Day Action Plan for Trade Compliance Teams

The December 2025 deadline has passed. If you're still running GTS 11, the following 90-day action plan will get you to a migration decision and into execution.

This 90-day plan forces a decision and prevents the "analysis paralysis" that many organizations fall into. The key is making the decision a business decision, not an IT procurement decision. Engage Finance and the business leadership. Don't let SAP's Account Team drive the timeline.

Related Reading

GTS 11 isn't the only SAP product reaching end-of-life. ECC (the current on-premise ERP platform) reaches end of mainstream support on December 31, 2027. Many organizations are facing multiple simultaneous migration decisions. These guides may help:

• SAP ECC End of Mainstream Support 2027: What it Means and What to Do
• The Complete S/4HANA Licensing Guide: What You'll Actually Pay
• SAP License Compliance: Avoiding Audit Overreach and Unnecessary Spend
• Third-Party SAP Maintenance: When and Why It Makes Sense