--- title: "Migrate away from OutSystems" url: "https://www.doddledesign.co.uk/services/outsystems-migrations" section: "Services" description: "Move applications off OutSystems onto a modern stack in 6 to 12 weeks, with a relatively fixed cost tied to your application object footprint. Lower run cost, no per-user or per-app licence escalation, and a stack your team can extend." publisher: "Doddle" --- [What we do](https://www.doddledesign.co.uk/services) Migrate away from OutSystems Other services[OutSystems Delivery](https://www.doddledesign.co.uk/services/outsystems-delivery) [AI-Native Delivery](https://www.doddledesign.co.uk/services/ai-native-delivery) [Consultancy Services](https://www.doddledesign.co.uk/services/consultancy-services) Re-platform # Migrate away from OutSystems. When OutSystems is no longer the right fit, we move applications to a modern stack in 6 to 12 weeks. You keep your governance, your monitoring and your operational confidence, and you pick up modern AI capability on the way. [Let's discuss](https://www.doddledesign.co.uk/contact) [Size a migration](https://www.doddledesign.co.uk/services/outsystems-migrations#calculator) ![A measured migration in progress](https://www.doddledesign.co.uk/images/outsystems-migrations.jpg) Why now ## Great platform. Sometimes the wrong fit. OutSystems is excellent for enterprise. We'd know - 18+ years on the platform, still shipping on it every week. Sometimes it stops being the right fit. Licence economics shift, strategy changes, an acquisition forces a replatform, or you want to go AI-Native on a more open stack. That's fine - everyone adapts to a changing landscape. The question for a business leader is how you move without giving up the control and assurance enterprise low-code gave you. And where you even start. The team best placed to help sits between the two worlds. Deep OutSystems experience, a growing portfolio of AI-Native builds and migrations. That's us. Decision framework ### Read where OutSystems still wins, and where it doesn't. A short framework for weighing whether OutSystems still fits your team in 2026, written by people who deliver on the platform every week. [Read the framework](https://www.doddledesign.co.uk/insights/outsystems-2026) [Let's discuss](https://www.doddledesign.co.uk/contact) [Try the ROI calculator](https://www.doddledesign.co.uk/services/outsystems-migrations#calculator) What to expect ## The worries teams ask us about, and the shape of the bill. The questions we get asked most - how the move actually runs, and what changes in your run cost on the other side. ### No source code or subscription change We scope from your application catalogue and a few interviews. Your OutSystems environment keeps running until you tell us the new one is ready, and your subscription only ends when you decide it should. ### Large estates move incrementally Hundreds of applications? We don't move them in one go. We pick the cleanest first, run it in production alongside the rest, then move the next in batches that suit your roadmap. ### Data migration is handled, not hand-waved The trickiest part of any move. We map data in discovery, build the new copy alongside the live one with reconciliation reports as we go, and only switch when the numbers line up. The old environment stays warm during cutover. ### Predictable run cost Run cost on the new stack barely moves with the number of applications or the number of users. Add another tenant or another mobile feature and the bill stays roughly flat. ### Every environment, included Dev, QA, pre-prod, prod, sandbox - whatever shape your team works in. The new stack doesn't charge a tier per environment, so we can match what you already have. ### Refresh, not just relocate Migration is the natural moment to retire the features no one uses, fix the UX that's been bugging everyone, and add the AI capabilities that didn't fit before. We pick those calls together in discovery. ### Quick to iterate on the other side On a modern stack with our delivery setup, teams iterate quickly with the same controls in place. Run cost goes down and ongoing delivery cost moves with it. Sizing ## Rough numbers, in under a minute. Pick the bands closest to your estate to see the cost shape, the run cost on the new stack, and the saving against what you're paying today. Discovery confirms the real numbers and locks the price. Migration sizing ### How big is your estate? Pick the bands that fit. We'll show the cost shape, the run cost on the new stack, and the saving against what you're paying today. Discovery confirms the real numbers and locks the price. Application objects (AO) 1503006008001,000+ Monthly active users 1k2k5k10k+ Current annual OutSystems spend I don't know<£50k£50–100k£100–500k£500k+ Your current OutSystems annual licence £56k estimated Pick a band on the left for a number closer to yours. Migration cost £50k–£70k Fixed-price after discovery Duration 6 weeks Users live throughout Annual run cost £3.3k–£5.3k All environments included Estimated annual saving £52k/yrpayback in 14 months Run cost on the new stack barely moves with more apps or users, so the saving compounds as you grow. Bands are indicative. Discovery runs from your application catalogue and a few interviews, so we don't need source code or touch your subscription to scope it. Not sure yet? ### Start with a one-week Estate audit. A lighter, earlier-stage engagement than Discovery. We look at your estate, map the art of the possible on a modern stack, and give you a written recommendation on whether a migration is the right next step at all. No source-code access required, and the audit fee is credited against Discovery if you proceed. [Book an Estate audit](https://www.doddledesign.co.uk/contact) Proof points ## What recent migrations have looked like. 300AO Migrated in six weeks. Small enterprise estate. 600AO Migrated in ten weeks. Mid-size estate, multi-team. 2weeks Fixed-price discovery. No source-code access needed. Why choose Doddle ## A senior team that knows the platform you're moving off. We've shipped migrations off OutSystems, and we still build on the platform. So the advice you get is neutral on the platform question, from a team that already knows what you're working with. ![Finbridge Global](https://www.doddledesign.co.uk/logos/finbridge-global.png) > “We started with Doddle on OutSystems, fast MVP, fast iteration. As we matured, they helped us move onto a full AI-native stack. The speed, the thinking, and the care in execution have been exceptional.” Barbara GottardiCEO, Finbridge GlobalRead the case study → ### 18+ years on the OutSystems platform We know what you're moving off, what you'll miss, what you won't, and what to replace it with. Sales & Delivery Partner since 2021. ### Two-plus years building with AI in production One of the things you pick up on the modern stack is native AI capability. We've been shipping production AI for real users for years, not learning on yours. ### A repeatable migration playbook Discovery, parallel build, cutover. Done end-to-end multiple times, with users on a working application throughout. Partnerships![OutSystems Sales & Delivery Partner](https://www.doddledesign.co.uk/logos/outsystems-logo.svg) ![Anthropic Claude](https://www.doddledesign.co.uk/logos/claude-code.svg) What moves across ## Every OutSystems pattern has a modern equivalent. We start by re-implementing what already works, beat for beat. Then we use the new stack to take it further, where it earns the change. Below is the surface area we cover by default, on O11 or ODC. Your applications land on a standard repository you own, with no platform licence and nothing locked behind a vendor. ### Workflows & BPT Approvals, case handling, long-running business processes. Rebuilt on modern workflow engines that keep the same behaviour and stay visible end to end. ### Timers & scheduled jobs Background work moves to standard infrastructure. Reliable, easy for your team to watch and extend. ### Client & server logic Clean separation between UI and the systems behind it. The two can evolve independently after the move. ### C# extensions & Forge Custom extensions and Forge component logic come across as first-class code. Easier to test, easier to share, no longer tied to platform internals. ### Mobile & PWA Native mobile and mobile-first PWA flows rebuilt with modern frameworks. Push, offline and biometrics handled by mature libraries. ### SSO, identity & roles Existing SSO, role models and audit trails preserved. We integrate with whichever IdP you already run. ### JavaScript & front-end Custom JS, screen logic and bespoke UI patterns re-implemented in modern frameworks, with a design-system baseline so the experience comes through cleaner. ### Data & integrations Existing data stores, REST and SOAP integrations, and ETL flows migrated in parallel and reconciled end-to-end before cutover. ### AI that does work end-to-end (new) A newer pattern that fits the modern stack naturally - AI that completes multi-step tasks on its own, under the same governance you'd apply anywhere else. Included at no extra cost. Migrations run from OutSystems 11 or ODC. Co-existence is supported during the cutover window, so users stay on a working application throughout. Why migrate with Doddle ## What you don't lose when you move. The thing teams worry about losing when they move off OutSystems is usually the stuff the platform handled silently in the background. The four pillars below cover the worries we hear most often - the rest of the practice sits underneath. ### Automated testing Tests at every level, run automatically on every change. Nothing ships without passing them. ### Code review & analysis Code is checked automatically for quality, security and architecture compliance. AI-written code is held to the same bar as human-written code. ### Visibility in production Cost, performance and quality on live dashboards. Every interaction can be replayed for debugging. Nothing hidden. ### Security built in Security woven through delivery, secrets, dependencies, vulnerabilities, not bolted on at the end. [Same harness underneath everything we build - see the full Engineering practice→](https://www.doddledesign.co.uk/engineering) Our approach ## Four phases. Most migrations inside twelve weeks. Discovery is the only paid commitment up front. It runs against the application catalogue and a few interviews, so there's no need to grant code access or change your OutSystems subscription before you've seen a plan. 01 ### Discovery 2 weeks, paid The scoping engagement once you've decided to move. We work from your application catalogue, a few interviews, and a short data audit. No source-code access required. Output is a migration plan, a fixed price for the move itself, and the lift-vs-refresh call on each application. (If you're not yet sure migrating is the right answer, the one-week Estate audit above is the starting point.) 02 ### Migration 4 to 12 weeks Incremental delivery, with users always on a working application. We move things in sensible batches, modernising where it earns the change. Data migration runs in parallel, validated end-to-end before any user is asked to switch. 03 ### Cutover 1 week Quiet switch. SSO, integrations, scheduled jobs all migrated. The old OutSystems environment stays warm during co-existence, so rollback is cheap if it's ever needed. 04 ### Support & enhance Your call Shipping isn't the moment we vanish. Most teams keep us in for one of three flavours - a support retainer for when the unexpected happens, continued enhancement while your team builds confidence, or a small care plan that keeps the pipeline, monitoring and AI capability fresh. We're equally happy training your team to take the lot in-house. We say what we'd recommend, then we do whatever fits. [Let's discuss](https://www.doddledesign.co.uk/contact) Is this the right track? ## Honest about when to pick this one. Good fit ### Right for you if… - Teams whose context has shifted and OutSystems no longer fits. - Applications where AI ambitions need a different runtime. - Estates where AO-driven licence economics have changed the maths. - Teams who want to move without losing governance or observability. [Scope a migration](https://www.doddledesign.co.uk/contact) Not the move ### Look elsewhere if… - Estates where OutSystems is still earning its keep. We'd rather you stay. - Migrations driven by fashion rather than fit. - When the right answer is a hybrid estate, not a full move. Probably a better fit [OutSystems Delivery](https://www.doddledesign.co.uk/services/outsystems-delivery) [Consultancy](https://www.doddledesign.co.uk/services/consultancy-services) Common questions ## The things teams ask us before they start. If something here is missing, ask us. We'll answer honestly and add it to this list for the next person. Do you need access to our OutSystems source code to scope a migration? No. Discovery runs from your application catalogue and a few interviews. We don't need to touch your existing OutSystems subscription, environments or code base to give you a fixed price. You only cancel anything when you choose to, after the move is done. How big can an estate be? Can you handle very large ones? Yes. For very large estates we recommend an incremental approach - pick one application, migrate it cleanly, run it alongside the rest, then move the next. That keeps risk small and lets the new setup prove itself before you commit to the whole portfolio. Some of our biggest engagements have started that way. What about data migration? That's usually the hardest part. It is. We've done this enough times to have a sensible playbook - map the data in discovery, build a parallel copy that reconciles against the live one, then switch when the numbers match. The old environment stays warm during cutover, so if anything looks off we can step back without panic. Are you abandoning OutSystems as a partner? Not at all. We've been on the platform for 18+ years, became a Sales and Delivery Partner in 2021, and we still deliver on OutSystems every week. The honest answer is that the platform is excellent for some contexts and the wrong fit for others. When the fit has shifted, this is what we do. What happens after the migration ships? Whatever you want. Some teams take the lot in-house and we just check in. Some keep us on a small support retainer that maintains the platform, watches monitoring and rolls in AI updates. Some keep us delivering features as their team builds confidence. We say what we'd recommend, and we work to that. Can we migrate from both OutSystems 11 and ODC? Yes, both. We've migrated from O11 and from ODC. The approach is the same - work from the catalogue, plan the lift, run a parallel build, switch. ODC migrations tend to be slightly faster because the surface area is cleaner. ## Thinking about moving off? Tell us the application catalogue and what's prompted the question. We'll come back with a view on time, cost, and whether moving is actually the right call. [hello@doddledesign.co.uk →](mailto:hello@doddledesign.co.uk) [Let's discuss](https://www.doddledesign.co.uk/contact) [Size it first](https://www.doddledesign.co.uk/services/outsystems-migrations#calculator) ## More from Doddle - [Studio summary for agents](https://www.doddledesign.co.uk/llms.txt) - [Full text of every page](https://www.doddledesign.co.uk/llms-full.txt) - [How to work with Doddle as an agent](https://www.doddledesign.co.uk/agent-instructions.md) - [Every page on the site](https://www.doddledesign.co.uk/sitemap.xml) - [Talk to a human](https://www.doddledesign.co.uk/contact) or email hello@doddledesign.co.uk