Contact Us

This field is for validation purposes and should be left unchanged.

Contact Us

This field is for validation purposes and should be left unchanged.

Data Migration for Legacy Applications: How Rivit Moves Years of Records Without Losing Context

By Rivit Technology Partners

Share this

Every data migration from a legacy application carries the same hidden risk. The records land in the new system, the row counts match, and weeks later users discover that approval histories, attachments, and access rules never made the trip. For organizations running Lotus Notes and HCL Domino, that risk is higher, because Domino stores business context inside documents instead of tables. Rivit has focused on this exact problem since 2011. UsingRevive Application Migrationand its built-in Data Migrator, Rivit moves years of records into modern databases with relationships, security, and history intact.

Rivit is a Lotus Notes and HCL Domino modernization specialist based in Vaughan, Ontario, serving enterprises and public sector organizations across North America. This guide explains why data migration from Domino applications goes wrong so often, what a failed data migration costs, and how Rivit plans, executes, and validates a data migration so the business keeps every record and the meaning behind it.

→ Is your organization putting off a Domino data migration because nobody is sure what the databases actually hold?Talk to Rivitand get a clear view of your data before you commit to anything.

Why Does Data Migration From Legacy Applications Lose So Much Context?

Most data migration tools were built for relational systems. They assume the source has tables, columns, keys, and a schema somebody documented. Domino applications rarely fit that model, and the gaps show up as lost context.

Domino stores each record as a self-contained document. A Notes document holds whatever fields the form saved at the time. Two documents created by the same application ten years apart can have different fields, different data types, and different meanings for the same field name. A data migration that reads only the current form design misses everything the older documents carry.

Rich text fields hold far more than text. A single rich text field can contain formatted paragraphs, tables, embedded images, file attachments, and links to other documents.HCL’s own developer documentationdescribes these fields as containers for text, tables, document links, bitmaps, and OLE objects, with a single field able to hold several megabytes. Flatten that into a plain text column and the record loses its supporting evidence.

Relationships live in formulas and lookups. Domino developers rarely used foreign keys. They linked records through @DbLookup formulas, response hierarchies, and document links. The relationship exists, but only inside the application logic. Move the data without reading the logic and the links break.

Security is stored on the record itself. Reader and Author fields control who can see and edit individual documents. A data migration that ignores them either exposes confidential records to everyone or locks out the people who need them.

Multi-value fields and computed values hide in plain sight. One Domino field can hold a list of names, dates, or approvers. Other values are computed when a document opens and never stored at all. Both need deliberate handling during data migration.

Years of workarounds add up. After two decades of use, many Domino applications carry orphaned responses, abandoned fields, and data patched by agents nobody remembers writing. Without an inventory of what exists, the data migration team discovers these problems during cutover instead of during planning.

→ Do your Domino applications store approvals, attachments, and access rules that a standard data migration tool would flatten or drop?Ask Rivithow much context your current plan would lose.

Two developers at a desktop monitor discussing a legacy application data migration plan

What Does a Failed Data Migration Cost the Business?

A data migration rarely fails loudly. The new application launches, and the problems surface one support ticket at a time.

Audit trails disappear. In regulated industries, the history attached to a record matters as much as the record. When approval chains, timestamps, and signoffs are dropped during data migration, the organization loses the evidence auditors and regulators expect to see.

Users stop trusting the new system. When people search for a contract and find the metadata without the attachment, they keep the old Notes client open “just in case.” Parallel systems mean paying for two platforms, and the legacy environment never actually retires.

Rework eats the budget. Teams that discover missing data after go-live often rerun the data migration, rebuild mappings by hand, and patch records one by one. A project scoped for months can stretch past a year.

The Domino environment stays alive. Many organizations alreadymoved their mail to Exchangeyears ago and tried SharePoint for simple databases. The complex applications stayed, partly because nobody could guarantee their data would survive the move. Meanwhile, HCL licensing costs keep rising, and the developers who understood these applications keep retiring. TheDomino support extensionbuys time, but it does not fix the underlying data migration problem.

→ Has a past data migration attempt left your team running Domino alongside a newer system?Contact Rivitto find out what it would take to finish the job and shut the old servers down.

How Does Rivit Approach Data Migration Differently?

Rivit runs data migration inside the application migration itself, with one team responsible for both. The application logic, the user interface, and the records move together, so the new system understands its own data on day one.

Rivit reads the application before it moves the data. Revive exports each Domino application to DXL and parses its forms, views, agents, script libraries, ACLs, and computed fields. Schema relationships, workflow patterns, and dependencies are mapped before a single record is converted. That analysis is what turns a document database into a defined SQL schema.

Mapping rules are generated from the schema analysis. Revive’s Data Migrator generates field mappings, foreign keys, and transformation rules from that schema analysis. Developers review and adjust them, but they do not write hundreds of mappings by hand. This is where Rivit saves the most time compared with a traditional data migration.

Business logic carries forward with the data. Revive translates selection formulas into database queries, computed fields into indexed search fields, and agents into scheduled jobs or REST endpoints. The original Domino code is kept as inline documentation, so developers can trace any migrated value back to the rule that created it.

Applications move one at a time. The original Domino application keeps running until its replacement is validated. Users keep working, and there is no portfolio-wide freeze. Each cutover is a controlled event with a known scope.

Costs are fixed after real analysis. Rivit prices data migration and application migration from measured complexity, with effort estimates targeted at plus or minus 20%. Finance teams get a defensible number instead of an estimate that grows during delivery.

Rivit also brings people who know the platform. The team has worked on Domino for more than 25 years, and Rivit describes it as the largest team of Notes and Domino specialists in North America. That experience matters when a data migration hits a field nobody has documented since 2004. To see how this combines with AI-assisted code conversion, read how Rivitrebuilds Domino applications in weeksinstead of years.

→ Would a fixed-price data migration, based on measured complexity, make it easier to get budget approval?Speak with Rivitabout scoping your first application.

How Rivit Uses AppAnalyzer to Plan Data Migration Before Any Record Moves

Every Rivit data migration starts withAppAnalyzer Migration Analysisat no cost to the client. Organizations that believe they run ten Domino databases often find they run two hundred or more. AppAnalyzer shows exactly what exists before anyone commits budget.

AppAnalyzer reports on application inventory, usage statistics, technical complexity, dependencies, and migration readiness. For data migration planning, that means the team knows which databases hold active records, which ones nobody has opened in years, how many documents each application stores, and which applications depend on each other through lookups.

That information shapes the plan. High-use applications with complex data relationships move through Revive. Inactive databases with retention requirements go to archiving. Redundant applications get retired. A clearapplication inventoryalso prevents the most common data migration surprise, which is discovering a dependent database halfway through a cutover.

AppAnalyzer output also supports the internal business case. CIOs and IT directors can show their CFO a documented portfolio, per-application cost estimates, and a sequenced roadmap. Many Rivit clients use the analysis to secure funding, then move into delivery.

→ Do you know how many Domino applications your organization runs and how much data each one holds?Request your AppAnalyzer assessmentand see the full picture at no cost.

Software engineer typing at a workstation while running a data migration batch import

Inside the Revive Data Migrator: How Rivit Moves Records, Attachments, and Security

Revive has three parts that work together. The Code Transformer rebuilds the application, Core Elements replace platform functions Domino used to provide, and the Data Migrator handles the records. Here is how the Data Migrator handles data migration in practice.

Schema to SQL mapping

Revive converts Domino forms and fields into a relational schema with field mappings, foreign keys, and transformation rules. Response hierarchies and lookup relationships become real database relationships, so reporting and integration work the way modern teams expect.

Automated transformations for difficult data

The Data Migrator applies automated transforms for the data types that break most tools. Domino names are converted into a usable format. Multi-value fields are split into proper structures. Rich text is converted for display in the new React interface, and file attachments move with the record they belong to.

Database adapters for your target platform

Pluggable adapters write to PostgreSQL, MySQL, Microsoft SQL Server, MongoDB, and Azure Cosmos DB. The migrated application runs on Java, Spring Boot, and React and deploys to Azure, AWS, Google Cloud, or on-premise servers. There is no proprietary runtime and no ongoing license fee after the data migration is complete.

Batch imports with full visibility

Large data migration runs execute as batch imports with progress tracking, monitoring, and the ability to cancel a run safely. Teams can see where a load stands instead of waiting overnight for a pass or fail result.

Reusable rules for repeatable cutovers

Mapping rules are stored per project and per database dialect. Rivit runs trial migrations, reviews the results with business owners, adjusts the rules, and runs the data migration again. When cutover day arrives, the final load uses rules that have already been tested several times.

Security that moves with the records

ACLs, groups, and directory entries are migrated from the Domino address book, and single sign-on connects the new application to modern authentication. Record-level access carries over, so confidential documents stay confidential after the move.

→ Are attachments, rich text, and record-level security the parts of your data migration that worry you most?Book a working session with Rivitto walk through how Revive handles your specific applications.

How Rivit Validates a Data Migration Before Cutover

Moving the data is only half the work. Rivit validates every data migration against the source before users switch over.

Validation starts with reconciliation. Document counts, field populations, and attachment counts are compared between Domino and the target database for each application. Business owners then test real scenarios, such as opening a five-year-old approval, checking its attachments, and confirming the right people can see it.

Because the original application stays live until sign-off, any gap found during validation is fixed by adjusting a rule and rerunning the load. Nobody is patching production records by hand under pressure. Migration history records every run, which gives auditors a clear trail showing what moved, when, and under which rules.

This discipline is how Rivit has handled projects such as abank branch operations platformbuilt on nine interconnected Domino databases, where losing the links between records was not an option.

→ Does your organization need audit-ready proof that every record survived the move?Contact Rivitto see how validation and reconciliation fit into your data migration plan.

What Does a Data Migration Project With Rivit Look Like?

Every engagement follows the same sequence, which keeps each data migration predictable for IT teams and business owners alike.

Analysis comes first. AppAnalyzer maps the portfolio, measures record volumes, and flags dependencies. Rivit and the client agree which applications move through Revive, which go to Dcom, and which get retired.

Code and schema are generated together. Revive turns each Domino export into a running Spring Boot and React application, often within hours, along with the SQL schema and the first draft of the mapping rules. Developers then complete the remaining logic with AI-assisted tooling.

Trial loads expose problems early. Rivit runs the data migration against a copy of production data, reviews the results with business owners, and refines the rules. Older documents with unusual field histories surface here, during planning, where they are cheap to fix.

Cutover is a scheduled event. Once validation passes, Rivit runs the final data migration, users switch to the new application, and the Domino version is retired or archived. The first applications typically reach users in weeks, and each later wave moves faster because the rules and patterns are already proven.

Rivit stays involved after go-live. Many clients keep working with Rivit through later waves and new development, so the knowledge gained during the first data migration carries into every application that follows.

→ Want to see what this sequence would look like for your first wave of applications?Schedule a planning call with Rivitand get a realistic timeline built from your own environment.

Developer comparing source and target records on dual monitors to validate a data migration

When Rivit Recommends Archiving Instead of Data Migration

Not every Domino database needs a full data migration. Some applications are no longer used, but their records must be kept for legal, regulatory, or historical reasons. Rebuilding those applications wastes money.

For these cases, Rivit usesDcom Application Archivingto preserve the records in a searchable archive with full-text search, PDF rendering, and compliance-grade retention. Users can still find and read historical documents, and the organization can finally turn off the Notes servers that held them. Combined withapplication rationalizationand a plan toretire legacy business systemssafely, archiving often cuts the scope of the full data migration significantly.

Which Industries Rely on Rivit for Data Migration?

Domino was most widely adopted by large enterprises and government institutions, and those are the organizations with the most records at stake. Rivit supports data migration projects across several sectors.

Banking and financial services. Banks and investment firms hold transaction records, client files, and approval histories that regulators can request years later. Rivit’sfinance and bankingwork includes branch operations platforms and investment accounting software built on Domino.

Government and civil agencies. Public sector teams face records retention laws and access to information requests. Rivit helpsgovernment and civil agenciesmove case files and correspondence while keeping access controls intact.

Life sciences, healthcare, and pharma. Validated systems, quality records, and research documentation need a defensible data migration with full traceability. Rivit supportslife sciences and healthcareorganizations andpharmacompanies with migrations that preserve record history.

Manufacturing. Engineering change requests, quality databases, and supplier records often run on Domino. Rivit’smanufacturingclients move this data without interrupting production workflows.

Utilities, transportation, and technology.Utilitiesoperators,transportation and logisticsfirms, andtechnologycompanies rely on Rivit for maintenance logs, operational records, and software platforms built on Domino. Tax software provider Vertex worked with Rivit whenmigrating its complex Domino applicationsoff the platform entirely.

→ Does your industry require you to prove that migrated records are complete and unchanged?Talk to Rivitabout data migration projects in your sector.

What Else Does Rivit Offer Beyond Data Migration?

Data migration is one part of a broader modernization program, and Rivit supports the full lifecycle.

Enterprise Application Developmentfor what comes next. Once data and applications are on a modern stack, Rivit helps clients extend them with new features, integrations, workflow automation, and APIs.

Infrastructure servicesfor the target environment. Rivit supports the cloud and on-premise environments the migrated applications and databases run on.

Revive Hub for a complete Domino exit. Revive Hub gives users one workspace with single sign-on and migrated access controls, replacing the Notes client entirely.

Strategy support for the whole portfolio. Rivit helps IT leaders turn analysis into anapplication modernization strategywith realistic sequencing and budgets.

Rivit works with organizations across Canada and the United States, delivering remote and on-site engagements for enterprises of every size that still depend on Domino.

→ Need one partner to handle analysis, data migration, archiving, and future development?Reach out to Rivitand build a single plan for your entire Domino portfolio.

Team of developers working at computers in an office on an enterprise data migration project

Data Migration With Rivit: FAQs

How does Rivit keep context intact during a Domino data migration?

Rivit reads the application design before moving any records. Revive parses forms, views, agents, and formulas, then generates mapping rules that preserve relationships, response hierarchies, attachments, and record-level security. The original Domino code is kept as documentation, so every migrated value can be traced back to its source logic.

Which databases can Rivit migrate Domino data into?

Revive’s Data Migrator includes adapters for PostgreSQL, MySQL, Microsoft SQL Server, MongoDB, and Azure Cosmos DB. The migrated applications run on Java, Spring Boot, and React, and can be deployed on Azure, AWS, Google Cloud, or on-premise servers.

Can Rivit migrate attachments and rich text from Notes documents?

Yes. Rivit’s Data Migrator applies automated transformations for rich text, file attachments, multi-value fields, and Domino names. Attachments stay linked to the records they belong to, and rich text content is converted for display in the new application.

Will Rivit need to shut down our Domino applications during the data migration?

No. Rivit migrates one application at a time, and the original Domino application keeps running until its replacement has been validated. Users keep working throughout, and each cutover is planned with business owners in advance.

How does Rivit estimate the cost of a data migration project?

Rivit starts with a no-cost AppAnalyzer assessment that measures application complexity, record volumes, and dependencies. Pricing is fixed from that analysis, with effort estimates targeted at plus or minus 20%, so there are no surprise change orders.

How does Rivit validate migrated data before go-live?

Rivit reconciles document counts, field values, and attachments between Domino and the target database, then has business owners test real scenarios. Mapping rules are adjusted and the data migration is rerun until results match, and every run is logged for audit purposes.

When does Rivit recommend archiving instead of a full data migration?

Rivit recommends Dcom archiving for applications that are no longer in active use but still hold records that must be retained. Dcom provides searchable, read-only access to historical documents so the organization can retire its Notes servers.

Does Rivit work with organizations outside Ontario?

Yes. Rivit is based in Vaughan, Ontario, and works with enterprises and public sector organizations across Canada and the United States on data migration and application modernization projects.

Data Migration With Rivit

A data migration from Domino succeeds when the business can open any record in the new system and find everything it had before: the attachments, the approvals, the history, and the right access rules. That outcome depends on reading the application along with the data.

Rivit combines AppAnalyzer’s portfolio analysis, Revive’s AI-assisted application and data migration, Dcom archiving, and a team that has worked on Domino for more than 25 years. Clients come away with a modern application their developers can support, a database their reporting tools can use, and a legacy platform they can finally switch off.

→ Is it time to move your Domino records somewhere your business can rely on for the next twenty years?Contact Rivitto start your data migration with a free analysis of your environment.

→ FollowRivit on LinkedInfor practical guidance on Domino modernization, application migration, and enterprise data strategy.

More Insights