What Happens If You Leave
A perpetual licence, a transferable AWS account with root access, and a complete handover package — the technical and contractual answer to lock-in, and it does not depend on April9 continuing to trade.
The Answer to “What If We Want to Leave?”
Most vendors answer lock-in questions with “trust us”. April9’s answer is contractual and technical — see how it compares in Stack9 vs a Traditional DXP.
Perpetual Licence
A licence to run Stack9 at its latest running version, surviving the end of the service relationship — though it carries no entitlement to later releases.
Transferable AWS Account
The solution runs in a dedicated AWS account provisioned for you, transferable with root access at any point — the whole running environment, not an export.
Open Data Formats
Structured data sits in Amazon Aurora, a standard relational database, extractable as SQL or CSV/JSON via REST; documents come native from S3.
Complete Handover Package
Source code, infrastructure-as-code, CI/CD pipelines, environment documentation, architecture diagrams and operational runbooks — everything needed to build, deploy and run the solution elsewhere.
What’s In It, on Transfer or Exit
- Source code — the code built specifically for your solution, not a generic platform export.
- Infrastructure-as-code definitions — the same definitions used to provision DEV, UAT and Production, so environments are rebuildable, not just documented.
- CI/CD pipelines — the automated build and deployment pipelines your team or the next provider can run directly.
- Environment & configuration documentation — what is provisioned, how it is configured, and why.
- Architecture diagrams — for every environment, showing how software, infrastructure and network components interoperate.
- Operational runbooks — the day-to-day operating procedures April9’s own team follows, handed over rather than kept in-house.
This is a complete operating package, not a one-click migration to another platform — another operator, or you, still has to build, deploy and run the solution from what is handed over.
In, and Out
Transitioning In
- A signed-off Project Initiation Document names approvers and milestones before any work starts.
- Environments are provisioned as infrastructure-as-code, authenticating against your directory, with synthetic test data only.
- Key users configure alongside April9 through the build, so capability transfers as the solution is built.
- Role-based training runs before go-live, followed by hypercare and then the 90-day warranty.
Transitioning Out
- A transition-out plan is agreed within 20 business days of request, or 6 months before end of term.
- Weekly meetings track progress, risk and stakeholder engagement for the duration of the transition.
- April9 assists with data extraction in open, non-proprietary formats — SQL, CSV/JSON, native documents.
- Data is retained online for at least six weeks, then completely removed, with written confirmation.
Ready to Talk About What Happens Next?
Whether you're scoping a new engagement or just want the exit terms in writing before you sign, we can walk through both.