If your organization runs Magic xpi 4.13 or an earlier version that uses GigaSpaces, planning your upgrade to Magic xpi 4.14 should be a priority.
Magic no longer contracts with GigaSpaces. Affected GigaSpaces licenses have expiration dates beginning as early as December 31, 2026, although some licenses expire later.
When your GigaSpaces license expires, all integration projects still using it will become non-operational.
Upgrading to Magic xpi 4.14 replaces GigaSpaces with Magic's own In-Memory Middleware (IMM), removing the GigaSpaces license expiration dependency. Here's what that means for your business and how to prepare.
First expirations
Dec 31, 2026
Some licenses expire later. Confirm yours.
At expiration
Projects stop
Anything still on GigaSpaces becomes non-operational.
The fix
xpi 4.14 + IMM
Magic-owned middleware, no license dependency.
Watch
Why do Magic xpi 4.13 customers need to upgrade?
Your integration platform connects the systems your business depends on. When those connections stop, the processes they support can stop moving too.
For organizations using affected GigaSpaces licenses, expiration creates a direct operational risk. Depending on your integration projects, that could interrupt order processing, inventory updates, customer data synchronization, production information, or other automated workflows.
This is more than a support milestone. Upon the applicable GigaSpaces license expiration, projects still using that middleware will become non-operational.
The first step is to confirm the expiration date for your specific environment with Magic Americas. Do not assume that every customer has the same deadline, or that a later date removes the need to upgrade.
What changes in Magic xpi 4.14?
The central change is the middleware supporting your integration environment.
Earlier versions used GigaSpaces. Magic xpi 4.14 uses Magic's own In-Memory Middleware, or IMM. This removes the GigaSpaces dependency and its associated license expiration.
Before and after the upgrade
Magic's xpi 4.14 release notes also describe these capabilities:
- Updated monitoring: A redesigned xpi Monitor with improved filtering and Azure single sign-on support.
- RESTful API integration: OpenAPI support and generation of starter flows for defined endpoints.
- Java-based Excel integration: Read and modify workbooks without installing Microsoft Excel on the runtime server.
For existing customers, continuity is the immediate reason to act. The newer capabilities provide additional opportunities once your integrations have been migrated and validated.
What if you already received a GigaSpaces extension?
Some customers previously received a fix that extended GigaSpaces operation.
If your organization received one, you should still plan your upgrade. An extension provides additional time, but your environment continues to depend on GigaSpaces and its applicable expiration date.
Magic Americas is prioritizing upgrades to xpi 4.14 rather than an ongoing cycle of repairs and extensions. Your migration plan should therefore focus on moving to IMM before your existing GigaSpaces license expires.
Confirm your current expiration date with our team, including any extension previously applied to your environment.
How to plan your Magic xpi 4.13 to 4.14 migration
A successful upgrade starts with understanding what is running today and what needs to work after the transition. The following planning steps help your team define the scope.
The migration plan
1. Confirm your version and expiration date
Document your exact Magic xpi version, including the maintenance release, and identify the environments using GigaSpaces.
Ask Magic Americas to confirm the applicable license expiration date. Include development, testing, and production environments in that conversation.
2. Identify critical integrations and dependencies
Create an inventory of your active integration projects and the systems they connect.
For each project, identify its business owner, schedule or trigger, connector dependencies, and operational importance. Include custom components and external services that may need additional review.
This helps your team prioritize testing around the workflows that matter most.
3. Review the target environment
Work with your Magic Americas contact to confirm the appropriate 4.14 release and deployment requirements.
Because the upgrade changes the middleware, planning should cover infrastructure, connectivity, monitoring, and administration as well as the integration projects themselves.
The exact work will depend on your starting version, deployment model, and configuration.
4. Test complete business workflows
Testing should verify that the business process completes correctly across connected systems.
For example, an order integration may need to demonstrate that an incoming order reaches the ERP, receives the expected validation, and returns the correct status to the originating application.
Include exception handling, scheduled processes, and representative transaction volumes in your test plan. Review the release notes for changes relevant to your starting version and connectors.
5. Schedule the production transition
Choose a rollout window that leaves time before license expiration to address issues discovered during preparation.
Assign owners for the transition, business validation, and post-upgrade monitoring. Agree on contingency procedures with your technical team before making the production change.
When should you start?
Start planning now, even if your license expires after December 31, 2026.
The window
Your upgrade timeline needs to accommodate more than installation. Infrastructure preparation, testing, business approvals, and scheduling all take time. Starting early gives your team room to resolve dependencies before expiration becomes an operational emergency.
You do not need to have a complete migration plan before contacting Magic Americas. Begin with your current version, the person responsible for your environment, and any timing constraints.
Frequently asked questions about the Magic xpi upgrade
Does every GigaSpaces license expire on December 31, 2026?
No. Affected licenses begin expiring as early as December 31, 2026, but some have later dates. Contact Magic Americas to confirm the expiration date that applies to your environment.
What happens when the GigaSpaces license expires?
All projects still using the expired GigaSpaces license will become non-operational. The business impact depends on the workflows those projects support.
Does Magic xpi 4.14 use GigaSpaces?
No. Magic xpi 4.14 replaces GigaSpaces with Magic’s own In-Memory Middleware (IMM), removing the GigaSpaces license expiration dependency.
Do we need to upgrade if we received an extension?
Yes. Magic Americas is asking customers on affected versions to upgrade to xpi 4.14. A previous extension provided additional time; it did not migrate your environment away from GigaSpaces.
How long does an xpi 4.13 to 4.14 migration take?
The timeline depends on your version, infrastructure, number of projects, connector dependencies, customizations, and testing requirements. An environment review is the starting point for estimating the work.
Can we assume our existing integrations will work without testing?
No. Validate your integrations in the target environment before the production transition. Your starting maintenance release and configuration determine which changes require attention.
Plan your Magic xpi 4.14 upgrade with Magic Americas
Your integrations support daily business operations. Give your team time to move them before GigaSpaces expiration interrupts their work.
Magic Americas can help you confirm your expiration date, review your environment, and define the next steps toward xpi 4.14.
Contact your Magic Americas account representative to start your upgrade assessment. Bring your current xpi version, integration owner, and preferred timing so we can begin planning the transition.
