FRP Is the Biggest Platform Shift in Retirement Recordkeeping History. Plan It Right.
The transition from OMNI and Relius to FRP will take years, span multiple phases, and touch every piece of your technology stack. We’ve been inside every version of OMNI — and we know exactly what this migration demands.
The Uncertainty Is the Problem
FIS has announced FRP as the next-generation recordkeeping platform. But the critical details — feature parity, migration tooling, release timelines — remain fluid. Product capabilities shift between versions. Release dates move. And the organizations that wait for perfect clarity before planning will find themselves scrambling when the deadline arrives.
Convergent has been through every OMNI upgrade and migration cycle in the industry. We don't need to wait for certainty — we know how to plan around it. We help organizations get FRP-ready today, regardless of where the product roadmap lands tomorrow.
What FRP Means for Your Platform
FRP isn't an upgrade. It's a re-architecture. Here's what that means in practice.
Hosted Architecture
FRP runs in the cloud. That means every on-premise integration, every local batch job, every custom file exchange has to be re-architected. The question isn’t whether you’ll migrate — it’s whether you’ll do it on your terms or scramble to meet someone else’s deadline.
Text Files & OmniScripts Are Gone
FRP no longer supports text files or OmniScripts. If your operations depend on custom scripts built over two decades, every single one needs to be inventoried, evaluated, and either migrated or replaced. We’ve already built tools to parse 35,000+ OmniScripts. We know what this takes.
API-Only Data Access
FRP stores data in a relational database — but it’s only accessible through APIs. No more direct queries. No more ad-hoc reporting against flat files. Every downstream system that touches participant data will need to be re-integrated.
Historical Data Migration
Decades of transaction history, participant records, and compliance data don’t just appear in the new system. Mapping historical data to FRP’s relational model — and ensuring it’s queryable, auditable, and accurate — is one of the most underestimated challenges of this transition.
A 2–4 Year Journey
This is not a weekend cutover. For most organizations, FRP migration will span multiple phases and multiple FRP versions before reaching the target state. The organizations that start planning now will be the ones that arrive on schedule.
40 Years of COBOL & VSAM
Can FRP truly replace four decades of battle-tested COBOL, VSAM files, and transaction codes? For some organizations, the answer is yes — eventually. For others, the reality is more nuanced. We help you understand which parts of your stack FRP absorbs and which you’ll need to rebuild.
What FRP Means for Relius Users
If you're running Relius, the FRP question is even more pressing. Relius will be sunset. That much is clear. What isn't clear is the timeline, the level of support during the transition, or the migration path FIS will ultimately provide.
We've helped Relius organizations navigate this uncertainty — some by preparing for FRP, others by evaluating and migrating to alternative recordkeeping platforms that better fit their long-term strategy. The right answer depends on your plan book, your customizations, and your operational reality. We help you find it.
Questions You Should Be Asking Right Now
If you can't answer these confidently, you're not ready for FRP. And that's exactly where we come in.
- 1Do you know which of your OmniScripts will break under FRP — and which can be migrated cleanly?
- 2Have you mapped every flat-file integration to FRP’s API model?
- 3What’s your plan for historical transaction data that predates the relational database?
- 4How will your nightly batch processes change under a hosted architecture?
- 5Have you identified which customizations FRP will absorb versus which you’ll need to rebuild?
- 6What’s your contingency if FRP timelines shift again?
- 7Is the FRP version you’re getting actually the modern Java/relational system — or the one that still runs in the COBOL world?
How Convergent Helps
We've completed 18 large-scale migrations, moved 21,000 plans and $300 billion in assets, and migrated 21 million lines of COBOL. FRP readiness is the next chapter — and we're already writing it with our clients.
- FRP readiness assessment and gap analysis
- OMNI version-specific migration planning
- OmniScript inventory, impact analysis, and conversion strategy
- Data migration architecture — VSAM and flat files to relational models
- Historical data preservation and query strategy
- API integration mapping and downstream system re-integration
- Custom script conversion planning and execution
- Alternative RKS evaluation for Relius users
- Multi-phase migration project management
- Dry-run methodology — three progressively rigorous dry runs before go-live
Proof Point: Leading Recordkeeper
700,000 participants. $20 billion in assets. 600+ plans. Zero-day blackout. 100% data accuracy. The largest single-platform retirement migration in recent industry history — and we delivered it.
Frequently Asked Questions
- What is FRP, and why is it such a significant change?
- FRP is FIS's next-generation, cloud-hosted recordkeeping platform — the successor to OMNI and Relius. It isn't an upgrade; it's a re-architecture. Text files and OmniScripts are gone, data is accessible only through APIs, and every on-premise integration has to be rebuilt. For most organizations the migration spans two to four years and multiple phases.
- Will my OmniScripts work on FRP?
- No. FRP no longer supports OmniScripts or text files. Every script built over the past two decades has to be inventoried, evaluated, and either migrated or replaced. We have built tooling to parse 35,000+ OmniScripts, so we can tell you which break, which convert cleanly, and which need to be rebuilt.
- How long does an FRP migration take?
- For most organizations, two to four years. It is not a weekend cutover — it spans multiple phases and often multiple FRP versions before reaching the target state. The organizations that start planning now are the ones that arrive on schedule.
- What does FRP mean for Relius users?
- Relius will be sunset. The timeline, the level of transition support, and the migration path FIS will ultimately provide remain unclear. Depending on your plan book and customizations, the right move may be preparing for FRP or evaluating an alternative recordkeeping platform. We help Relius organizations decide which path fits their long-term strategy.
- How is data accessed in FRP?
- FRP stores data in a relational database, but it's only reachable through APIs — no direct queries and no ad-hoc reporting against flat files. Every downstream system that touches participant data has to be re-integrated against the API model.
- Can FRP replace 40 years of COBOL, VSAM, and custom transaction codes?
- For some organizations, eventually yes; for others the reality is more nuanced. The key is understanding which parts of your stack FRP absorbs and which you will need to rebuild. We help you map that out before you commit to a timeline.
From the Library
Further reading on FRP and platform migration
Research, articles, and case studies from our practice on migration strategy and operational economics.
The Translation Gap
Why Most Retirement Technology Modernization Fails — And What the Winners Do Differently
The future of retirement technology will not be won by the firms with the most tools, the biggest teams, or the loudest AI announcements. It will be won by the firms that can translate domain knowledge into technical execution faster than their competitors.
The FRP Question Every TPA Needs to Answer in 2026
FIS keeps pushing FRP timelines. If you're a TPA running Relius, here's what you need to decide — and what you need to know before you decide.
Read article
Cracking the Retirement Profitability Puzzle
Why Most Recordkeepers Can't Tell You Which Plans Actually Make Money — and What It Takes to Find Out
A Convergent perspective on operational complexity, platform consolidation, and the hidden economics of retirement plan administration. Account balances have no statistical relationship to servicing cost — and that gap is where margin disappears.
Don’t wait for FRP to define your timeline. Define it yourself.
Book a 30-minute FRP readiness assessment with a principal-level consultant who has been inside the OMNI platform for decades — not someone who read about it last week.