Most Domino migration programs stall at the same point. Leadership approves the idea, someone asks which applications should go first, and nobody can answer with confidence. A migration readiness assessment fixes that by measuring every Lotus Notes and HCL Domino application before a single line of code is rewritten.
At Rivit Technology Partners, we run that assessment throughAppAnalyzer migration analysisso your team can see usage, complexity, dependencies, and cost for each application in one place. This guide explains what a migration readiness assessment should show you, how Rivit runs one, and how the results become a migration plan your CFO will sign.
Rivit has worked with Notes and Domino since 2011, and our team includes people who have built on the platform for more than 25 years. From our base in Vaughan, Ontario, we support enterprises across Canada and the United States with what we believe is the largest team of Notes Domino experts in North America. Every migration readiness assessment we run is led by consultants who have built, maintained, and migrated Domino applications, supported by AI tools we built for this exact work.
→ Does your organization know how many Domino applications it is still running? Rivit can show you with a no-cost AppAnalyzer assessment, socontact our teamto request one.
Why Do Most Domino Migration Plans Stall Before the First Application Moves?
The decision to leave Domino is usually made years before anything moves. Mail went to Exchange or Microsoft 365 long ago. What remains is the application layer: approval workflows, document libraries, engineering databases, compliance logs, and custom tools that teams still use every day. The plan stalls because the organization cannot see that layer clearly enough to act on it.
Nobody knows how many applications exist. Domino applications spread through departments for decades. Business units built their own databases, copied templates, and replicated them across servers. In our experience, a company that believes it has 10 Domino databases almost always has more than 200. Without an accurate count, every budget conversation starts on a guess.
The people who built them have retired. The developers who wrote most enterprise Notes applications started their careers in the 1990s. Many have left, and the ones who remain are often the last person who understands a critical system. When that knowledge walks out the door, the documentation usually leaves with it.
Estimates come back too large to approve. Traditional rewrite proposals for a large Domino estate often land between $1 million and $5 million with timelines of 18 months or longer. Finance teams struggle to approve that without proof that the scope is real. So the project gets deferred, and the platform gets more expensive to keep.
The cost of staying keeps rising. HCL has raised licensing costs and pushed version upgrades across its customer base. Every year of delay adds renewal fees, upgrade work, and more reliance on outside support just to keep applications running. Our analysis of theDomino support extensioncovers why extended support buys time without solving the underlying risk.
Earlier fixes only covered the easy applications. Many organizations moved their simple databases to SharePoint or a low-code platform years ago. That worked for basic document libraries. Applications with LotusScript, multi-step approvals, or complex access rules stayed behind on Domino, and they are usually the ones the business depends on most.
Each of these problems has the same root. The organization is trying to plan a migration without data. A migration readiness assessment replaces assumptions with facts about every application, which is why it should be the first step of any Domino exit.
→ Has your last migration estimate come back too high to approve? Rivit can rebuild your scope from real application data, sospeak with a Rivit consultantabout a fact-based estimate.

What Should a Migration Readiness Assessment Actually Tell You?
A migration readiness assessment is a structured review of your application portfolio that scores each application on how ready it is to move, what it will take to move, and whether it should move at all. A good one answers business questions as well as technical ones.
At a minimum, a useful migration readiness assessment should tell you:
- How many applications you have, where they live, and who owns them
- Which applications people actually use, and how often
- How complex each application is, including LotusScript, agents, workflows, and integrations
- Which applications depend on each other or share data
- Which applications can be retired, which should be archived, and which need to be migrated or rebuilt
- What each migration will cost and how long it will take
- What order the applications should move in
That last point is where most assessments fall short. A spreadsheet of databases is anapplication inventoryand a necessary starting point, but it does not tell you what to do on Monday. Readiness is about sequencing. Some applications are simple, heavily used, and have few dependencies. They are ideal first moves because they deliver visible results and build confidence. Others are deeply connected to finance, compliance, or operations systems and need careful planning before anyone touches them.
Microsoft makes the same point in itsCloud Adoption Framework guidanceon workload discovery, which recommends prioritizing workloads and grouping dependent systems into migration waves. The principle applies directly to Domino. A migration readiness assessment that ignores dependencies will produce a plan that breaks the first time an application moves and a connected one stops working.
A migration readiness assessment also feedsapplication rationalizationdecisions. When you can see that 40% of your databases have not been opened in two years, the conversation shifts from “how do we migrate everything” to “what do we need to keep.” That shift alone can reduce migration scope substantially.
→ Do you have an inventory but no clear sequence for what moves first? Rivit can turn your application list into a ranked migration plan, sobook a call with our teamto see how.
How Does Rivit AppAnalyzer Run a Migration Readiness Assessment?
AppAnalyzer is the platform Rivit built to analyze Domino environments at scale. It reads application design, code, data, and usage, then produces the evidence our consultants need to build a migration plan. Here is how a Rivit migration readiness assessment works from start to finish.
Step 1: Discover every application in the environment
AppAnalyzer scans your Domino servers and builds a complete list of databases and templates, including the copies and replicas that manual inventories usually miss. Each application is tied to its server, template, and owner where that information exists. This gives your team the true size of the portfolio, often for the first time.
Step 2: Measure real usage
Usage is the fastest way to reduce scope. AppAnalyzer looks at activity across every application so you can see which ones are opened daily, which ones are touched once a quarter, and which ones nobody has used in years. Applications with no recent activity become candidates for retirement or archiving instead of migration.
In large environments, this step alone often removes a significant share of the portfolio from the migration budget. It also gives business owners hard evidence when they are asked to sign off on retiring an application they assumed was still in use, which shortens what is usually a slow approval process.
Step 3: Score technical complexity
AppAnalyzer breaks down each application’s forms, views, agents, LotusScript, formula language, and embedded logic. It flags the elements that drive effort, such as heavy custom code, external calls, and complex approval chains. Complexity scores let your architects compare applications on the same scale instead of relying on someone’s memory.
Step 4: Map dependencies and integrations
Many Domino applications pull data from other databases or push it to external systems. AppAnalyzer maps those connections so you can see which applications need to move together and which can move alone. This is the step that prevents one migration from breaking three other processes without anyone noticing until users call the help desk.
Step 5: Produce the technical blueprint
AppAnalyzer documents what each application does and how it was built, which matters most when the original developers are gone. For a business unit at one major Canadian financial institution where nobody left understood the applications, AppAnalyzer produced a 40-page technical blueprint in days.
Step 6: Estimate cost and effort
Because Rivit’s estimates come from analysis of the actual code, they are far more reliable than estimates based on interviews and database counts. Our effort estimates typically land within about 20% of actual effort, which gives finance teams a number they can trust.
Step 7: Deliver the readiness plan
Rivit consultants review the AppAnalyzer output with your team and turn it into a ranked plan. Every application receives a recommended path and a place in the migration sequence. You leave with a document you can take to leadership, procurement, and finance.
→ Are your Domino applications undocumented and owned by people who are close to retirement? Rivit’s AppAnalyzer can document them before that knowledge is lost, sorequest your assessmentwhile your experts are still available.
How Rivit Decides What You Are Ready to Move First
The headline result of a Rivit migration readiness assessment is a clear answer to the question that stalls most programs: where do we start? We group every application into one of five paths based on the AppAnalyzer data.
Move first
These applications are used regularly, have moderate or low complexity, and have few dependencies. They are the best early candidates because they show working results within weeks and give your users a first look at the modern interface. Early wins also make it easier to secure budget for the harder applications that follow.
A typical first group might include a departmental request tracker, a policy library, and a contract approval workflow. Each one is used every week, none of them depends on another system, and moving them gives your team a working example of the new platform within the first phase of the program.
Move next, in groups
Applications that share data or call each other move together as a wave. The migration readiness assessment shows which applications belong in each group, so connected processes stay intact when they move.
Rebuild or extend
Some applications are so central to the business that a like-for-like move is only the starting point. These are candidates for Rivit’sEnterprise Application Developmentteam, who can migrate the core logic and then add new features, integrations, or reporting once the application is on a modern stack.
Archive
Applications that hold records you must keep, but that nobody updates, do not need to be migrated. They can be archived with full search and compliance retention, which lets you shut down servers sooner.
Retire
Applications with no meaningful usage and no retention requirement can be decommissioned. Ourapplication decommissioningapproach makes sure retirement is documented and signed off by the business owner.
This grouping changes the economics of the project. When a large share of the portfolio is archived or retired, the migration budget goes toward the applications your business depends on. It also gives your team a sequence that fits your ownmodernization strategyand budget cycle, instead of a single large project that has to be approved all at once.
→ Would it help to know which applications you could move in the next quarter? Rivit can identify your best first candidates, sotalk to Rivitabout a readiness review of your portfolio.

What Makes a Rivit Migration Readiness Assessment Different?
Plenty of firms will offer to review a Domino environment. What separates Rivit is that our migration readiness assessment is built on the same technology and the same team that will carry out the migration.
The assessment is free to start. AppAnalyzer is offered as a no-cost assessment so you can understand scope before you commit budget. You get real data about your environment without a large discovery invoice.
Our estimates are built from the code itself. Many assessments rely on workshops where application owners describe what they think their systems do. AppAnalyzer reads the applications themselves. That is why Rivit can offer fixed-cost engagements based on actual analysis, with no scope creep and no surprise change orders.
The assessment connects directly to migration. The data AppAnalyzer gathers feeds straight into Revive, Rivit’s AI-powered migration platform. Nothing is lost between planning and delivery, and the application that was assessed is the same one that gets migrated.
We know both sides of the move. Our consultants understand Domino design, LotusScript, and replication in depth, and they also build modern applications on Java, Spring Boot, React, and SQL databases. That matters when an assessment has to judge how a Domino feature will behave on a new platform.
We measure success the way finance does. Our work on thetrue impact of a Domino migrationlooks past code conversion to licensing savings, support risk, and staff time. A Rivit migration readiness assessment frames its findings in those same terms so your business case holds up.
We work at enterprise scale. Rivit regularly assesses portfolios with hundreds of Domino applications, including environments of 500 to 1,000 applications spread across business units. AppAnalyzer handles that volume automatically, so a large estate does not mean a long or expensive discovery phase.
These differences matter most to organizations that have already tried and failed. If an earlier project moved simple databases to SharePoint and left the complex applications behind, a migration readiness assessment from Rivit shows exactly why those applications stayed and what it will take to move them now. Many of the commonmigration roadblockswe see trace back to plans that were built without this data.
→ Did a previous migration attempt leave your most complex applications behind on Domino? Rivit can show you what it will take to finish the job, soreach out to our teamto discuss your remaining applications.
What Happens After Your Rivit Migration Readiness Assessment?
A migration readiness assessment is only useful if it leads somewhere. With Rivit, each path in your plan connects to a specific solution, delivered by the same team.
Revive migrates the applications you are ready to move
Revive application migrationis Rivit’s AI-powered platform for moving Domino applications to a modern open stack. Revive automatically converts 70% or more of the code, drawing on more than 4,000 verified conversion patterns, while Rivit developers guide the rest. Applications land on Java, Spring Boot, React, and PostgreSQL, MySQL, or Microsoft SQL Server, with no proprietary runtime. Projects typically cost 20% to 25% of a traditional rewrite, and Rivit delivers working applications in weeks.
Revive moves applications one at a time. Your existing Domino application keeps running until its replacement is validated, so users see no disruption. Workflows, approval chains, access controls, and data relationships are preserved, which means users get the same functionality in a modern interface on day one. Rivit’s work onAI-assisted Notes migrationexplains how the AI and human review work together.
Dcom archives what you need to keep
Dcom application archivinghandles the applications your migration readiness assessment marks for archiving. Dcom preserves Domino data with full-text search, PDF rendering, and compliance-grade retention, so you can turn off Notes servers without losing historical records.
Enterprise Application Development extends what matters most
For applications that need more than a like-for-like move, Rivit’s development team builds on the migrated foundation with new workflows, integrations, APIs, and reporting. Because the migrated code is standard Java and React, your own developers can maintain it too. That removes the dependency on scarce Domino skills and makes it easier to hire, since any developer coming out of school can support the stack.
Infrastructure services support the move
Rivit’sInfrastructure servicesteam helps prepare the target environment, whether that is Azure, AWS, Google Cloud, or your own data center. Because the output is standard open-source technology, you choose where it runs and you pay no ongoing license fees once the migration is complete.
This connected model is what makes the readiness plan practical. Your team works with one partner for planning and delivery. Rivit’slegacy system modernizationwork runs from assessment through migration, archiving, and long-term development under one team.
→ Are you paying Domino licensing fees on applications that could already be running on a modern stack? Rivit can move your first applications in weeks, soschedule a conversationabout your Revive migration.

Which Industries Rely on Rivit for a Migration Readiness Assessment?
Rivit works with mid-sized and large organizations that run mission-critical applications on Domino. A migration readiness assessment matters most in industries where downtime, data loss, or a compliance gap would be costly.
Banks and lenders infinance and bankingmarkets often run branch operations, lending approvals, and audit trails on Domino. Rivit has modernized a major bank’sbranch operations platformand helped other financial institutions document applications no internal team could explain.
Government and civil agenciesface retention rules and security reviews that make dependency mapping and archiving a priority. We have seen federal IT risk teams flag Domino as a critical risk when only one staff member could still support it.
Inlife sciences and healthcareandpharmaorganizations, Domino applications frequently hold validated records and quality processes. A migration readiness assessment identifies which records need compliant archiving and which processes need to move intact.
Companies inmanufacturingoften run engineering change and quality applications on Domino. Operators in utilities rely on it for maintenance and safety records, and firms intransportation and logisticsuse it for dispatch, fleet, and compliance tracking. These systems tend to have deep dependencies, which is exactly what AppAnalyzer maps.
Rivit serves clients across North America. Our team is based in Vaughan, Ontario, and we deliver assessments and migrations for enterprises throughout Canada and the United States.
→ Is your industry’s compliance or uptime requirement holding back your Domino exit? Rivit can build a readiness plan around those constraints, soconnect with our teamto talk through your requirements.
Migration Readiness Assessment with Rivit: FAQs
What is included in a Rivit migration readiness assessment?
A Rivit migration readiness assessment includes a full application inventory, usage analysis, complexity scoring, dependency mapping, technical documentation, cost and effort estimates, and a ranked migration plan. Each application receives a recommended path, whether that is migration with Revive, archiving with Dcom, rebuilding, or retirement.
Is the Rivit AppAnalyzer assessment really free?
It is. Rivit offers AppAnalyzer as a no-cost assessment so organizations can understand the scope of their Domino environment before committing budget. There is no obligation to proceed with a migration afterward.
How long does a Rivit migration readiness assessment take?
Timelines depend on the size of your environment, but AppAnalyzer works quickly because it analyzes applications automatically. Rivit has produced detailed technical blueprints for complex business units in days rather than months.
How accurate are Rivit’s migration cost estimates?
Rivit’s effort estimates typically land within about 20% of actual effort because they are based on analysis of the application code itself. That accuracy is what allows Rivit to offer fixed-cost migration engagements.
Can Rivit assess applications that have no documentation?
Absolutely. Missing documentation is one of the most common reasons organizations contact Rivit. AppAnalyzer reads the application design and code directly and produces documentation that explains what each application does and how it works.
Does Rivit help decide which Domino applications to retire or archive?
Usage data from AppAnalyzer shows which applications are inactive, and Rivit consultants work with your business owners to confirm retention needs. Applications with records to keep go to Dcom archiving, and the rest can be decommissioned.
What platforms does Rivit migrate Domino applications to?
Rivit’s Revive platform migrates Domino applications to an open stack built on Java, Spring Boot, React, and SQL databases such as PostgreSQL, MySQL, and Microsoft SQL Server. The applications can run on Azure, AWS, Google Cloud, or on premises.
Does Rivit work with organizations outside Ontario?
Yes. Rivit is based in Vaughan, Ontario, and works with enterprises across Canada and the United States, delivering assessments and migrations for organizations throughout North America.

Your Rivit Migration Readiness Assessment
A Domino exit becomes manageable once you can see what you have. A migration readiness assessment from Rivit shows how many applications you run, which ones people use, how complex each one is, and what order they should move in.
AppAnalyzer gathers the evidence, our consultants turn it into a plan, and Revive, Dcom, and our development team carry it out. You get a fixed scope, an estimate your finance team can trust, and a first group of applications you can move with confidence. The sooner that work starts, the sooner your licensing costs and support risk start to fall.
→ Ready to find out which of your Domino applications can move first?Contact Rivitto start your no-cost AppAnalyzer assessment today.
→ FollowRivit on LinkedInfor ongoing insights on Domino migration, application modernization, and enterprise software.