Most legacy application migration projects run into trouble long before anyone writes new code. The trouble starts at the planning stage, when nobody knows how many applications exist, which ones people still use, or what each one depends on. Rivit plans every legacy application migration around facts pulled from your actual environment.
AppAnalyzer maps the portfolio,Rivit’s Revive platformconverts the applications worth keeping, and each one goes live only after your business owners confirm it works. This guide shows how Rivit takes a Lotus Notes or HCL Domino estate from first inventory to go live, one controlled step at a time.
Rivit has helped organizations modernize Notes and Domino applications since 2011, and its consultants bring more than 25 years of hands-on experience with the platform. The company is based in Vaughan, Ontario, and has the largest team of Notes Domino experts in North America, delivering legacy application migration projects for enterprises and public sector organizations across Canada and the United States.
→ Does your organization run Notes or Domino applications that nobody has fully mapped?Talk to Rivitabout a no-cost AppAnalyzer assessment and see what your migration would involve before you commit to a budget.
Why Does Legacy Application Migration Stall Before It Starts?
Most enterprises moved their Lotus Notes email to Microsoft Exchange or Microsoft 365 years ago. The applications stayed behind. Approval workflows, document libraries, engineering databases, compliance trackers and case management tools built on Domino are still running in banks, government agencies, manufacturers and hospitals. Many have been in production for 20 years or more, and the business depends on them every day.
When leadership finally asks for a legacy application migration plan, the same problems tend to surface.
Nobody knows the real size of the portfolio. Domino made it easy for any department to build its own application, so applications multiplied without central oversight. An organization that believes it runs 20 Domino databases often finds more than 200 once someone counts properly. A properapplication inventoryusually changes the scope, the budget and the timeline of the whole project.
The people who built the applications have retired. Most Domino developers started their careers in the 1990s. Many have left the workforce, and the documentation they left behind is thin or missing. Younger developers rarely want to learn LotusScript and Formula language, so the knowledge gap grows every year.
Traditional proposals are too expensive to approve. A manual rewrite of a complex Domino portfolio often comes back at $1 million to $5 million or more, with timelines past 18 months. A legacy application migration avoids risk rather than generating new revenue, which makes that kind of number very hard to defend in front of a CFO.
Earlier replacements failed for complex applications. SharePoint and low-code tools handled simple databases well. Applications with LotusScript agents, multi-level approval chains and field-level security did not fit, and those are the applications still running on Domino today. Teams that hit theseNotes application migration roadblocksonce are understandably cautious about trying again.
Staying on Domino keeps getting more expensive. HCL has raised licensing costs and pushed customers toward version upgrades. HCL has also moved the end of Extended Support for Domino 9, 10 and 11 to June 30, 2030, as shown on theHCL Domino product lifecycle pagefor those versions.
That coverage still requires Standard Support and a separate statement of work with HCL. The extra time is useful only if organizations spend it planning the move, because theDomino support extensiondoes nothing to replace retiring developers.

What Should a Legacy Application Migration Plan Include?
A workable legacy application migration plan answers a set of practical questions before any code changes hands. Which applications exist, and who actually uses them? Which ones should move to a new platform, which should be archived, and which can be shut off? What does each application depend on, such as shared address books, lookups into other databases, scheduled agents, or connections to systems like SAP and Active Directory?
The plan also needs to capture the security model. Domino applications control access through ACLs, roles, and reader and author fields, and those rules often carry regulatory weight. If the new application loses them, the organization has a compliance problem on day one.
Data matters just as much. Years of documents, formatted content, attachments and audit history have to arrive intact and stay searchable. Finally, the plan has to define the target platform, the cost, the order of migration, how each application will be tested, and who owns it once it goes live.
Governance is the piece most teams underestimate. A legacy application migration touches dozens of business units, and each one has an application owner who must approve scope, testing and cutover dates. Without named owners and a clear sign-off process, projects drift. Rivit builds that ownership into the plan from the first week, so every application has a business sponsor before conversion begins.
Generic frameworks such as the “6 Rs” (rehost, replatform, refactor, repurchase, retire and retain) give teams a shared vocabulary. For Domino, though, rehosting only moves the same platform onto new servers. Most organizations end up choosing between converting, replacing, archiving and retiring each application, which is whyapplication rationalizationbelongs early in the process. This is the stage where a broadapplication modernization strategybecomes a sequenced project plan with owners and dates.
→ Has your team tried to scope a Domino migration and ended up with more questions than answers?Contact Rivitto get a portfolio-level view of what you have and a realistic plan for moving it.
How Does Rivit Plan a Legacy Application Migration From First Inventory to Go Live?
Rivit runs every legacy application migration through the same sequence. Each stage produces something your team can review and approve before the next one begins. Decisions rest on evidence from your own servers, and nobody has to guess at scope, cost or risk.
Stage 1: Rivit maps the portfolio with AppAnalyzer
Every engagement starts withAppAnalyzer migration analysisacross your Domino environment. AppAnalyzer is Rivit’s AI-powered discovery platform. It catalogs every database and template, records usage statistics, and measures the design complexity of each application, including forms, views, agents, LotusScript, Java and Formula code.
AppAnalyzer also maps dependencies between applications and external systems. The output is a technical blueprint with complexity scores, effort estimates and migration readiness for every application, including the ones nobody inside the organization understands anymore. Rivit’s effort estimates typically land within 20% of actual effort, which gives IT leaders numbers they can put in front of a steering committee.
For many organizations, this is the first time anyone has seen the whole Domino estate in one place. Enterprise architects can see which applications share data, application managers can see which databases still have active users, and infrastructure managers can see which servers can be retired first. That shared picture is the foundation of every legacy application migration Rivit plans.
Rivit offers AppAnalyzer as a no-cost assessment. Many organizations use the results to build the internal business case and secure budget, before they have committed a dollar to the legacy application migration itself.
Stage 2: Rivit sorts each application into migrate, archive or retire
Usage data usually shows that a large share of the portfolio no longer needs to run as a live application. Some databases have not been opened in years. Others hold records the organization must keep for legal or regulatory reasons, but nobody needs to edit them.
Rivit works with your application owners to place each application in one of three groups. Active, business-critical applications move forward for conversion with Revive. Applications that hold historical records go to Dcom, Rivit’s archiving product, where data stays searchable and compliant without a Domino server. Applications with no remaining value are retired using soundapplication decommissioningpractices. Archiving and retiring first also shrinks the scope, and therefore the cost, of the conversion work that follows.
Rivit then sets the migration order. Priority usually goes to applications with the highest business risk, the fewest remaining support resources, or the strongest dependencies that other applications rely on. Many clients start with a pilot application that proves the approach to stakeholders before the larger waves begin.
Stage 3: Rivit sets a fixed price based on real analysis
Because AppAnalyzer has already measured every application, Rivit can quote a legacy application migration at a fixed price based on actual complexity. That price is typically 20% to 25% of what a traditional manual migration would cost.
Fixed pricing changes the conversation with finance. A traditional estimate often grows as developers discover undocumented logic halfway through the project. Rivit has already found that logic during analysis, so there are no surprise change orders and no budget that triples during delivery. CIOs get a business case they can defend to the CFO and the board.
→ Are you holding off on a migration because nobody can give you a cost you trust?Ask Rivitfor a fixed price built on an analysis of your actual applications.
Stage 4: Revive converts the applications
Revive is Rivit’s AI-powered application migration platform. It reads each Domino application’s forms, views, agents and LotusScript, then regenerates the application on a modern open stack: a Java and Spring Boot back end, a React front end, and a SQL database such as PostgreSQL, MySQL or Microsoft SQL Server.
Revive draws on more than 4,000 verified conversion patterns and automates over 70% of the code conversion. Rivit’s engineers handle the remaining work, focusing on the custom logic, integrations and edge cases where human judgment matters. This combination cuts migration effort by 70% to 90% compared with a manual rewrite. Purpose-builtAI-assisted IBM Notes migration also produces very different results from generic AI coding tools, which tend to miss the business rules buried in older code.
Revive carries forward the parts of an application that matter most to the business. Workflows, approval chains, business rules, ACLs and data relationships move across intact instead of being reverse engineered from scratch. Documents, attachments and history move with them, and the new application connects to modern authentication systems. You choose where it runs: Microsoft Azure, AWS, Google Cloud or your own data center.
Data migration runs as part of the same process. Rivit maps Domino documents and fields to relational tables, moves attachments and response hierarchies, and reconciles record counts so your team can confirm that nothing was lost. Data is moved automatically, without manual rekeying, and a final synchronization takes place just before each application goes live.
Stage 5: Business owners validate each application before cutover
The original Domino application keeps running while its replacement is tested. Your business users work through the new version with real data and confirm that every form, view, workflow and permission behaves the way it did before. Acceptance criteria are agreed during planning, so everyone knows what “done” means.
Revive produces like-for-like functionality in a modern interface. Users recognize their screens and steps, which keeps retraining to a minimum on day one. Rivit fixes any gaps the testers find before the application is approved for go live.
This validation step is where a legacy application migration earns the trust of the business. Application owners see their own records, their own approvals and their own reports in the new system. Regulated teams get documented test results they can file as evidence, and IT leaders get a clear, recorded decision before anything is switched over.
Stage 6: Rivit takes each application live one at a time
Rivit avoids big-bang cutovers. Each application goes live on its own schedule, after a final data synchronization and sign-off from its owner. The old Domino version is then set to read-only, archived with Dcom, or shut down, depending on what the planning stage decided.
As applications move, the Domino footprint shrinks. Once the last application is live, the organization can retire its Domino servers and stop paying HCL licensing fees. Rivit stays engaged after go live to support the new applications, and many clients compare results against the baseline AppAnalyzer captured to report theimpact of the migrationto leadership.

What a Rivit legacy application migration timeline looks like
AppAnalyzer results usually arrive within days of access being granted, and the planning stage turns those results into a prioritized roadmap and a fixed quote. A pilot application then goes through conversion, validation and go live, giving stakeholders a working example before larger waves begin. After that, applications move in groups sized to your team’s capacity for testing. Rivit agrees the pace with you, so the legacy application migration fits around busy periods such as fiscal year end or audit season.
→ Is your organization worried that a migration will disrupt the teams who depend on these applications every day?Speak with Rivitabout an application-by-application plan that keeps every system running until its replacement is approved.
Why Rivit’s Legacy Application Migration Approach Carries Less Risk
Every legacy application migration carries risk. Rivit’s process is designed to reduce that risk at each stage of the project.
Decisions start with data. AppAnalyzer measures the portfolio before any commitment is made. Scope, cost and timeline come from your actual applications instead of interviews and assumptions.
The old system keeps running. No application is switched off until its replacement has passed user testing. If something needs another look, the business continues on Domino while Rivit resolves it.
Business logic is preserved. Revive translates the logic that already exists. Your organization keeps the rules and workflows it refined over decades, and nobody has to rediscover them through months of requirements workshops.
Pricing is fixed before work starts. A fixed price based on real analysis removes the budget overruns that stall many migration programs halfway through.
Your organization owns an open stack. The output is standard Java, Spring Boot, React and SQL. There is no proprietary runtime and no ongoing license fee once the migration is complete, and any developer coming out of school can support the code.
Domino specialists lead every project. Rivit focuses entirely on Notes and Domino modernization. Its consultants know how these applications were built, which is why they can find hidden dependencies that general software firms miss.
One team stays accountable. The same Rivit specialists who run the assessment also plan, convert, validate and support each application. Nothing gets lost in handoffs between an analysis vendor, a development shop and a support provider.
Timelines shrink from years to weeks. Work that once required a year or more of manual development can now produce working applications in weeks, which lets IT leaders finish modernization inside a normal planning horizon.
→ Have past migration proposals stalled over cost, timeline or risk?Reach out to Rivitand compare those proposals with a fixed-price, application-by-application plan.

Which Industries Trust Rivit With Legacy Application Migration?
Domino spread widely through large enterprises and government institutions in the 1990s and 2000s, so Rivit’s clients come from sectors where applications are business-critical and often regulated.
Financial services organizationsdepend on Domino for branch operations, lending workflows and investment accounting. Rivit hasmodernized a major bank’s branch operations platformand moved a Domino-based investment accounting product to a modern stack, preserving audit trails and access controls throughout.
Government and civil agenciesoften run case management and records applications that IT risk teams have flagged as a critical exposure. A fixed-price plan helps these agencies move quickly once funding is approved.
Life sciences and healthcareorganizations andpharmacompanies rely on Domino for quality systems, document control and validated processes. Rivit’s validation stage gives these teams the evidence they need for regulators.
Manufacturingfirms run engineering change, supplier and quality applications on Domino, many built at plant level. AppAnalyzer is especially useful here because these portfolios tend to be larger than anyone expects.
Technology companiesthat built commercial products on Domino face a different problem, because their customers depend on the software. Rivit helped tax software providerVertex overcome the challengesof migrating complex Domino applications without disrupting its business.
Rivit also supportstransportation and logisticsoperators andutilitiesproviders, where dispatch, maintenance and compliance applications cannot go offline. Wherever your teams are located in North America, Rivit delivers the same process with the same specialist team. Every legacy application migration follows the same sequence of inventory, planning, conversion, validation and go live, whatever the sector.
→ Does your industry add regulatory or uptime pressure to your Domino migration?Connect with Rivitto talk with consultants who have handled applications like yours.
What Else Does Rivit Offer Alongside Legacy Application Migration?
A legacy application migration often reveals other needs, and Rivit covers them with the same team. That keeps one partner accountable for the whole Domino exit, from the first scan to the last server shutdown.
Dcom application archivingpreserves Domino databases that no longer need to run as live applications. Dcom provides full-text search, PDF rendering and compliance-grade retention, so organizations can finally turn off their Notes servers.
Enterprise application developmentpicks up where migration ends. Once an application runs on a modern stack, Rivit’s developers can add features, build integrations and APIs, or replace an application entirely with custom software.
Rivit’s infrastructure servicessupport the environments your new applications run on, whether in the cloud or on premises.
If your mail still lives on Domino, Rivit can also help youmigrate Lotus Domino to Exchangeas part of the wider program. For organizations planning broaderlegacy system modernizationbeyond Domino, Rivit’s consultants can advise on how the migration fits into that roadmap.
→ Would it help to manage archiving, migration and new development with one partner?Get in touch with Rivitto plan the full program in one conversation.

Legacy Application Migration FAQs With Rivit
How long does a legacy application migration with Rivit take?
Timelines depend on the size and complexity of the portfolio, which AppAnalyzer measures before work begins. Because Revive automates over 70% of the code conversion, Rivit typically delivers working applications in weeks rather than the 18 months or more that manual rewrites often require. A pilot application usually goes live first, so stakeholders see results early in the legacy application migration.
What does Rivit’s AppAnalyzer assessment include, and what does it cost?
AppAnalyzer catalogs every Domino application, measures usage and design complexity, maps dependencies and produces effort estimates. Rivit offers the assessment at no cost, and many clients use the results to build their internal business case.
How does Rivit price a legacy application migration?
Rivit quotes a fixed price after analyzing your applications. Pricing reflects actual complexity and is typically 20% to 25% of the cost of a traditional migration, with no surprise change orders.
Does Rivit preserve existing workflows and business rules?
Yes. Revive carries forward workflows, approval chains, business rules, ACLs and data relationships from the original Domino application. Your business logic is translated rather than rebuilt from memory.
Will users need retraining after Rivit migrates an application?
Very little. Rivit delivers like-for-like functionality in a modern interface, so users recognize their screens and steps from the first day.
Which technology stack and hosting options does Rivit migrate applications to?
Rivit migrates applications to an open stack built on Java, Spring Boot, React and SQL databases such as PostgreSQL. You can host the result on Microsoft Azure, AWS, Google Cloud or on premises, with no proprietary runtime or ongoing license fees.
What does Rivit do with applications that should not be migrated?
Applications that only hold historical records can be archived with Dcom, which keeps them searchable and compliant. Applications with no remaining value are retired, and Rivit helps you decommission them safely.
Can Rivit migrate applications with no documentation and no remaining developers?
Yes. AppAnalyzer produces a technical blueprint from the application design itself, so Rivit can map and migrate applications that nobody inside the organization understands anymore.
Planning a Legacy Application Migration With Rivit
A successful legacy application migration starts with knowing exactly what you have. Rivit begins with an AppAnalyzer inventory, sorts every application into migrate, archive or retire, fixes the price, converts the right applications with Revive, and takes each one live only after your business owners approve it. Y
our Domino applications keep running until their replacements are proven, your business logic survives the move, and your organization ends up with an open stack it can support for years. Rivit’s specialists have planned this work across banking, government, healthcare and manufacturing, and they can plan yours.
→ Ready to find out what your Domino portfolio really contains and what moving it would cost?Book your AppAnalyzer assessment with Rivitand start planning your migration with real numbers.
→ FollowRivit on LinkedInfor practical Domino modernization insights.