INVO
Talk to an ExpertTalk to an Expert
Data migration

Your data does not start from zero.We move it with you.

Changing systems should not mean rebuilding years of records by hand. We take the data out of your current systems and files, map it to the INVO model, clean it, normalize it and prepare it for migration. Where the source allows, we enrich it against our own data structures and reference sets. You start work in INVO with an environment that is already populated.

Talk to us about your dataSee the migration process

Your data today

  • ERP
  • Spreadsheets
  • WMS
  • MES
  • PLM & BOM data
  • In-house systems

INVO data migration

  1. 01 Mapping
  2. 02 Cleaning
  3. 03 Normalization
  4. 04 Enrichment
  5. 05 Validation

INVO

Data ready for the first working day.

Your data

We move the data your organization actually runs on.

The scope is agreed individually at the start of the rollout. Depending on the modules in play, we can prepare the following for import.

Components and products

  • Part numbers
  • Names
  • Categories
  • Units of measure
  • Conversion factors
  • Airframes and sub-assemblies
  • Part revisions

Bills of materials

  • Components
  • Quantities
  • BOM structures
  • Sub-assemblies
  • Build variants
  • Product–BOM links

Suppliers and purchasing

  • Suppliers
  • Supplier item codes
  • Price lists
  • Commercial terms
  • Purchasing data
  • Component–supplier links

Inventory

  • Warehouses
  • Locations
  • Inventory levels
  • Lots and serials
  • Item configuration

Customers and contracts

  • Customers
  • Programs
  • Billing data
  • Price lists
  • Contract structures
  • Delivery schedules

Operating data

  • Selected history
  • Data needed to continue current processes
  • Agreed within the project scope

No two migrations look the same. Together we decide which data is needed to start the system, which is worth keeping for history, and which does not belong in the new environment at all.

Migration process

From source data to data ready to work with.

Migration is not a single file import. It is a controlled process made up of several stages.

  1. 01DiscoverWe find the data sources.
  2. 02MapWe map the data to INVO.
  3. 03CleanWe clean up the records.
  4. 04NormalizeWe normalize the structure.
  5. 05EnrichWe enrich where the source allows.
  6. 06ValidateWe validate the data.
  7. 07ImportWe load it into INVO.

Stage 01 — Discover

We find the data sources.

We establish where the data lives, who owns it, which formats the organization uses, which source is the master, and which records have to move at all.

  • Where does the data live?
  • Who owns it?
  • Which formats does the organization use?
  • Which source is the master?
  • Which data has to move?

Typical sources

  • ERP
  • Spreadsheets
  • WMS
  • MES
  • SQL
  • CSV
  • In-house systems

Better data in, better system out

The old system’s problems do not have to move with it.

In most organizations master data grew over years. Different teams invented their own names, part numbers, categories and helper files, so the same component can exist under several names, in different units, with incomplete information. Migration is the moment to sort that out.

Before migration

Name
mtr 2807 1300kv
Unit
PCS
Category
none
Extra information
none

After data preparation

Name
Motor 2807-1300KV
Type
Component
Category
Motors & ESCs
Base unit
pc
Links
BOMs · Suppliers · Airframes

Where enrichment can reach

  • Classification

    Product categories and groups.

  • Units

    Base units and their conversion factors.

  • BOM structures

    Links between components and sub-assemblies.

  • Supplier data

    Your item codes matched to supplier item codes.

  • Compliance

    The export-control and conformity data parts need.

  • Production

    Data structures used in planning and execution.

How far enrichment goes depends on what the source data supports and on the agreed scope of the rollout. Migration can be a data-quality project, not just a transfer.

Consolidation

Your data does not have to sit in one system today.

In a real organization the information needed for a rollout is usually scattered across several systems, spreadsheets and files.

  • ERPProducts and suppliers
  • Spreadsheet 01BOMs
  • Spreadsheet 02Price lists
  • WMSInventory levels
  • Production systemRoutings and test records
  • Local filesEverything else

Mapping + consolidation

The INVO data model

One consistent set of records, prepared for migration.

We do not require perfect input data.

We do not expect you to complete the following before the project starts:

  • Tidy every spreadsheet
  • Rebuild your item codes
  • Standardize every name
  • Prepare a perfect data model for INVO

That work is part of the migration. We need access to the source data and to the people who understand what it means. The rest we go through together, in a controlled process.

Validation before go-live

Data problems should not surface on launch day.

Before the system goes live, the data can be imported and checked in a test environment, so teams get to run real scenarios first.

End-to-end test

  1. Component
  2. BOM
  3. Production schedule
  4. Requirement
  5. Purchase
  6. Inventory
  7. Production

We test processes, not record counts.

We do not simply check that 10,000 records arrived. We check that the processes using those records behave correctly.

  • Purchasing

    Verifies suppliers and purchasing item codes.

  • Production

    Checks airframes, sub-assemblies and their BOMs.

  • Warehouse

    Verifies part numbers, units and warehouse structure.

  • Engineering / R&D

    Verifies BOMs, revisions and variants.

Ready for day one

On launch day you do not start from an empty system.

The final migration is part of the launch plan. Before go-live we agree the following.

  • Scope of the final data set
  • When the source extract is taken
  • Import sequence
  • Validation
  • Responsibilities
  • Readiness criteria

Cutover

  1. 01Source data
  2. 02Final extract
  3. 03Transformation
  4. 04Validation
  5. 05Production import
  6. 06Go-live

After launch, a user should open INVO and find an environment ready for their work. Not an empty installation.

Data migration

From the data you have today to data ready for what comes next.

Migration into INVO is a controlled process, run in eight steps.

  1. 01

    Discover

    the data sources

  2. 02

    Map

    the old model to INVO

  3. 03

    Clean

    the quality problems

  4. 04

    Normalize

    the data structure

  5. 05

    Enrich

    where the source allows

  6. 06

    Validate

    data and processes

  7. 07

    Import

    into INVO

  8. 08

    Launch

    with the data already in place

We do not expect you to prepare perfect data for our system. We help turn the data you have today into a structure ready to work in INVO.

Data migration

Let’s look at what needs to move into INVO.

In a first analysis we can walk through your current data sources together, set the migration scope and agree how the data gets prepared for launch.

Talk to us about your dataBook a demo

Continue exploring implementation

Discovery & Process MappingHow you really work today.IntegrationsConnect INVO to your stack.Implementation overviewEvery area in one place.