Migrating Eclipse RCP Applications
Eclipse RCP applications often carry well over a decade of investment: proven domain logic, refined workflows and users who know their tool inside out. Many of them will keep running for years. That gives you the chance to migrate on your own terms, before user expectations, a shrinking pool of RCP expertise or an external constraint set the timeline for you. Not planning a migration yet? See how we support and evolve existing RCP applications.
Migrating off RCP is a re-architecture. We have spent close to two decades in the Eclipse RCP ecosystem and, for more than a decade, built web-based tools alongside it, on Eclipse Theia, as VS Code extensions and as custom web applications. We evaluate component by component what to reuse, reimplement, redesign or retire. Proven domain logic can often be extracted into headless components that serve the browser, a Theia-based tool or a VS Code extension, for example via the Language Server Protocol (LSP). Components that would carry OSGi or SWT dependencies into the new architecture are often cheaper to rebuild cleanly. The same patterns let the existing and the new tool share functionality, so your users can keep working while both run side by side.
AI-Assisted Migration
AI has changed what a migration costs to execute. It now speeds up a large share of the implementation-heavy work: mapping an unfamiliar code base, writing characterization tests that pin down current behavior, extracting business logic from the UI, rebuilding the UI on a web stack, and the many adapters and refactorings in between. Migrations that were shelved as too expensive a few years ago deserve a second look.
The judgment calls stay with people. Important behavior in an RCP application hides in plugin manifests, extension points, OSGi services and platform behavior, not only in Java source. Reading it correctly takes engineers who know RCP in depth, know the target architectures and have practical experience applying AI to real code bases. It also takes your team, who know the domain and the history behind the design, which is why we work closely with them. The gains from AI depend on that combined experience.
Migration Strategy Workshops
Before committing to a migration, most teams want a clear target architecture and a realistic roadmap. We work these out in a structured workshop engagement: your team brings the domain knowledge and the history of the application, and we bring experience with RCP, the target stacks and AI-assisted migration. Topics and depth depend on the package and your application, and typically include:
- Status quo and architecture review: the existing system from a user and an architecture perspective, key use cases, which features are still needed, and critical migration aspects
- Architecture options: viable target architectures, what to reuse or reimplement, and the trade-offs
- Target architecture: a deep-dive into the most promising option(s), working towards a concrete target vision
- Migration strategy: the migration approach, the transition phase, possible PoC scopes and opportunities for AI-assisted migration
- Roadmap and effort estimation: a roadmap with milestones and indicative effort for the full migration, informed by PoC results where applicable
The workshops usually run remotely. We capture the results in a report, slide deck or similar material that outlines the architecture options, the recommended target and the roadmap. Your team can build on it whether it carries out the migration on its own, with our support, or with us implementing parts of it.
Explore the Workshop PackagesMigration Workshop Packages
The Architecture package gives you a solid basis for deciding whether and how to migrate. The larger packages add a proof of concept and a code inspection, which reduce risk and sharpen the effort estimate.
The prices are meant as guidance. The right scope depends on the size, characteristics and complexity of your application, so we define the final package together with you. For very large applications that have grown over many years, we often start with selected subsystems or an MVP scope. Get in touch with us to tailor a package to your needs, and ask us about special conditions for first engagements.
Architecture
€7,2001A sound basis for planning and decisions
- Status quo and architecture review
✓ - Architecture options and trade-offs
✓ - Target architecture vision
✓ - Migration strategy incl. AI opportunities
✓ - Roadmap and effort estimate
High-level - Proof of concept with demo
× - Code inspection and AI potential assessment
×
PoC-Validated
€12,0001Working evidence and a demo for stakeholders
- Status quo and architecture review
✓ - Architecture options and trade-offs
✓ - Target architecture vision
✓ - Migration strategy incl. AI opportunities
✓ - Roadmap and effort estimate
PoC-validated - Proof of concept with demo
Focused - Code inspection and AI potential assessment
×
Comprehensive
€18,8001Sharper estimates for larger migrations
- Status quo and architecture review
✓ - Architecture options and trade-offs
✓ - Target architecture vision
✓ - Migration strategy incl. AI opportunities
✓ - Roadmap and effort estimate
Refined - Proof of concept with demo
Broader - Code inspection and AI potential assessment
✓
(1) Indicative package price, excl. VAT. The final scope and price depend on your application and are agreed with you before the engagement starts.
RCP Support and Maintenance
Many RCP applications will stay in productive use for years, whether or not a migration is planned, and they have to keep running well. EclipseSource has close to two decades of experience with Eclipse RCP applications in domains such as finance, transportation, aviation, insurance, automotive and semiconductors. We support teams from bug fixes and performance improvements to updating to recent Eclipse and Java versions, moving builds to Maven Tycho, or migrating from Eclipse 3.x to Eclipse 4 (e4). AI-assisted development speeds up this work too, in the hands of engineers who know RCP well. Where it makes sense, we shape these steps so that they also prepare a later migration, for example by separating business logic from the UI.
Staying on RCP can be a sound decision for a stable application with a limited remaining lifetime, predictable requirements and secured maintenance expertise. If your application is expected to evolve for another five or ten years, a migration strategy is worth having early. Our Architecture package is a low-commitment way to work it out together. For new projects, we usually recommend a web-based foundation, and we are happy to discuss the trade-offs.
Also see our Developer Support offering and our service offerings for IDEs and tools.
RCP Training and Workshops
Working efficiently on an Eclipse RCP application requires familiarity with a number of core concepts, from OSGi and the workbench to SWT, JFace and the Eclipse 4 application model. EclipseSource has trained developers in Eclipse RCP since its inception and has RCP experts on staff who have authored several books on the topic. Our training is a good fit for teams who maintain an RCP application or take over an existing code base, including Eclipse RCP Development, Eclipse 4 (e4) and e4 migration training. We also run individual workshops on project-specific topics, and if your team is preparing for a migration, we can combine RCP know-how with an introduction to the target technologies. Get in contact with us to discuss the best training options for your team.
Also see our training offerings in general and the Eclipse 4 tutorial series.
Sponsored Development and LTS
Eclipse RCP has proven to be a remarkably stable platform. Still, specific use cases sometimes require bug fixes or enhancements in the platform itself, and long-lived applications may need to stay on a specific platform version for a while. Since Eclipse RCP is open source and neutrally governed, such fixes can be contributed upstream. You do not have to port them to every new version yourself, and the technology you rely on stays sustainable. We have committers on the relevant core technologies and can make these contributions for you via sponsored development. We also provide long-term support, so that older platform versions remain maintainable for your project while you plan its future.
Get in contact with us to discuss how to keep your application and the platform stable for the long term.
What our customers say
Let's talk about your RCP application
Whether you are planning a migration, exploring your options or need support for your existing application, we are happy to hear from you.
Contact Us










