Map a forward path for your IBM Notes and Domino applications based on comprehensive data analytics.


Systematically scans your Domino servers and database designs

Adviser’s comprehensive, detailed analysis provides you with a complete list of your applications and templates, reveals the true business usage of these applications, and ranks their complexity.


Presents complex, sophisticated data in a simple and intuitive web interface

The user interface for Adviser is a web application and is hosted on a Domino server. The controls are interactive and intuitive, and much of the data is presented in graphical form.


Recommends a forward path for each application

The guidance module sorts potentially thousands of applications and instructs whether they should be maintained or rewritten, archived, retired, or replaced. This recommendation is based on a combination of the application usage, design complexity, and business value of each database.


Simplifies the decision-making process surrounding your existing Domino servers and Notes applications

Uncertainty about what to do with highly customized, native Notes applications is common. Adviser provides clarity through comprehensive data, helping you make confident decisions about your databases and environment.

The Way Forward

Before you can make decisions about what to do next with your IBM Notes applications, you need to gather a lot of information about the nature of those applications. Trying to understand how many apps you have, how complex they are, which are being used and by whom, and their business value is a complex and intensely time-consuming undertaking. Adviser scans your Domino servers and database designs, intelligently aggregates the data, and provides you with your unique roadmap to what’s next for your applications. Adviser contains four modules: Catalog, Usage, Complexity, and Guidance.


The catalog module reads information from your Domino servers and provides a core list of databases and templates. You can use the catalog to browse your databases by name, server, template or how recently they’ve been modified. In addition to information pulled from the server, this module also allows you to set a Business Value for each database, tracking its importance to your organization. Lastly, the catalog module allows you to configure filters to exclude certain databases from the other Adviser modules.


The usage module imports usage information from your Domino servers and displays detailed usage statistics for both users and databases. For a database, you can see how many times it was accessed and by whom, along with historical trends showing whether the usage is increasing or decreasing. For a user, you can see which databases and servers they have accessed.


The complexity module scans the complete designs of the databases on your servers and generates a complexity score, which measures the approximate difficulty of moving your applications to what's next. The score is based on a number of factors including the size of the design and the numbers of different types of design elements, along with counts of specific Domino features that are hard to migrate. You can also specify keywords whose presence suggest that migration may be difficult. These include, for example, references to other proprietary internal systems or external code in DLLs.


The guidance module brings together information from all the other modules to make a recommendation on a forward path for each database. Its recommendation is based on a combination of the application usage, the design complexity, and the business value of each database. You may also override the recommendation in cases where you already have a plan for a given database.

The guidance module’s recommendation will be one of four options:

  • Retain: The application needs to be maintained or rewritten on a new platform. This can be a lengthy and expensive course of action and is only recommended for applications with very high business value and usage.
  • Archive: The application contains valuable data that should still be available to your users, but a read-only archive is probably enough.
  • Retire: The application can be backed up based on your data retention requirements, and removed.
  • Generic: The application can be replaced with an off-the-shelf product. Simple discussion databases or document libraries are an excellent example of generic applications.

Armed with this information, you can confidently begin rewriting, archiving, retiring, or replacing your applications.

Data Sheet

View or download a one-page data sheet for Teamstudio Adviser.


We were there when you built your first database.
Count on us now as you move to what's next.

“Catalog Scan and Usage Auditor have been extremely useful in finding all the applications (databases) in our environment, along with tracking vital usage information on each application. This information can then be consolidated from each server and extracted to create a usage metric, thus allowing us to make informed decisions in regards to what applications stay and which ones should be removed.”
— George Bartha, Unifrax

We'll schedule time with you for an in-depth, virtual demonstration.

Receive pricing and product information over the phone or through email.