3 Steps to Migrate Domino Servers to Azure

This is the last in our series about migrating IBM Domino servers to Microsoft Azure. In earlier posts, we talked about the benefits of moving your Domino server workloads to the cloud, why they’re a great place to start, and key challenges to watch out for. Here, we share our three-step process to make the migration happen.

Migrating your Domino servers from your data center to Azure’s IaaS platform is a significant, but cost-effective, decision for any organization. To keep things simple, we use a three-step migration process to help our clients manage and execute this effort, shown below.

 Domino on Azure Migration | Binary Tree

Step 1: Discovery

First up, we catalog your Domino server workloads, everything from applications to storage. Here are examples of actions we take in each area.

Applications and servers

  • Discover Domino server workloads and the hardware they run on
  • Inventory any Notes applications on each Domino server
  • Identify any dependences on these Notes applications
  • Find any non-Domino applications that might be running on your Windows or Linux servers


Analyze your network, including:

  • Configuration
  • Firewalls
  • Security
  • Addressing requirements 


  • Discover how much storage space you need for each Domino server workload
  • Plan for enough space to grow over time
  • Record baseline metrics on disk usage
  • Use these to determine the appropriate disk types on Azure
  • Allocate the right level of maximum IOPS for each virtual disk 


  • Record baseline metrics for your computing usage over 1 week
  • Use this to estimate how much processing power you need to run your workloads

Open issues

  • Check your server logs for any issues that are causing performance problems now
  • Also look for any errors that might cause issues down the road

Step 2: Assessment

In this next phase, we categorize and set targets for your workloads.

Applications and servers

  • Analyze what we found in our discovery scans
  • Look for opportunities to consolidate your workloads

Operating system

  • Make recommendations on the operating system to use for the Azure virtual machines

Domino server versions

  • Consider replicating your Domino server workloads to new servers running in Azure
  • Figure out which Domino server version to use in the Azure virtual machines


Plan the virtual network requirements, including:

  • IP addressing
  • Subnets
  • Firewalls and IP filters
  • Traffic flow policies
  • Access control lists
  • Network security groups
  • Load balancers
  • Site-to-site VPN vs a WAN link


The amount of storage space for your workloads is important. But we also want to make sure that we optimize your storage. That is, we consider the right level of storage throughput (IOPS / MBps) for each virtual disk.


We review the baseline metrics on your computing usage. This gives us a good idea of how much processing power you need to run your workloads. We don’t recommend auto-scaling Virtual Machines for Domino servers. Instead, we recommend matching on the appropriate VM type and size. We base the performance requirements on Azure Compute Units.

Open issues

  • Go over any errors or issues that we find in the logs
  • Determine if any of these affect the migration planning
  • Fix any errors or issues that might slow or block your migration


We create a migration plan. This is where we do things like:

  • Create a prerequisites checklist
  • List tasks that must be completed by your organization
  • List recommended Azure resources to support your workloads
  • Create a new Azure environment with networking and virtual machines
  • Plan how and in what order to move the workloads
  • Define the transition of connections between on-premises servers to the Azure servers

This is an example of the type of plan we set up (without resources or a RACI matrix):

Domino to Azure Migration | Binary Tree

Step 3: Migration

Last up, we execute our migration plan. These are the types of things we do in this phase:

  • Move workloads to a new Azure platform
  • Track how we’re progressing against the plan
  • Finalize and document configurations and settings
  • Send required communications
  • Transition servers to operations
  • Take other actions as needed to wrap up the migration

Get started

If you’d like help with moving your workloads to Azure, Binary Tree would be happy to walk you through it in more detail. See more about how we can help you solve your Domino server challenges, or contact us to discuss all our digital transformation solutions.