NavOne Migration

Mission Statement

Our client was embarking on a migration from a legacy system to TrustQuay’s NavOne.

The client had already purchased Alteryx Licences from Continuum prior to the migration. In addition, they also had an experienced user employed within the company meaning they could undertake much of the work themselves.

Tools Used

Alteryx

- API Connector

- Reconciliation against existing data

- Alteryx Server

Detailed Solution

The first step was to connect the client’s data to Alteryx to provide data quality and gap analysis as shown in the diagram below.

The client has two choices at this stage;

  1. Resolve all issues at source (recommended)

  2. Plug the gaps with mappings and default values, both possible and transparent in our reusable workflows.

Data Migration NavOne

Then we recreated the import templates for NavOne from the actual client data each time they were ready to populate the system for testing.

The re-runnable model means that we could do multiple migrations to an empty system allowing all their test cycles to take place on real data, identifying issues early.

We also repeatably pseudonymised the data as the client needed to use a test domain.

A quote from our satisfied client:

“Using Alteryx enabled us to perform a highly complex data migration into Trust Quay’s NavOne product.

We were able to create a robust and repeatable process with no need for complex coding or database skills.

This saved a huge amount of time and allowed for more focus on testing and data transformation during migration, resulting in a cleaner final data set.”