• Albatross - migration with Extraction, Transformation and Load agents

    Three agents move your data.
    You sign off.

    Migrate with Albatross: an Extraction Agent, a Transformation Agent and a Load Agent carry your data from the old system into the new one.

    Your sources, Extraction Agent, Transformation Agent, Load Agent, your destination - a person signs off after each agent
    Meet the agents
  • Albatross - A Free ETL Data Migration Platform

    Wearing the right hat
    for migration?

    Explore Albatross Data Migrator to see if you are.
    De-Risk your migration with the proven ETL platform.

    Explore
  • Albatross - Data Migration Platform based on ETL

    DATA VARIATIONS NOT FITTING
    THE SYSTEMS?

    Albatross Data Transformer can help ease it

    Explore The Transformer in Action

Albatross architecture as agents

Three agents do the legwork of your migration. Your people make the calls.

Migrate with Albatross and the work splits three ways. The Extraction Agent reads your old systems, the Transformation Agent reshapes what it finds to fit the new one, and the Load Agent puts it there. Between each of them sits a sign-off from the people who own the data.

Albatross architecture as three agents. Your sources (ERP and PLM, legacy databases, spreadsheets, data files, file servers, big-data stores) flow into the Extraction Agent, then the Transformation Agent, then the Load Agent, which loads into enterprise systems, RDBMS and big data, cloud systems, or apps on Helios and Flow on Pragmatos. You approve the report, the maps and the load in between.

Extraction Agent

Talks to the sources you already have.

Connects through adapters, profiles volumes, formats, older versions, missing files and references, then runs the pre-migration checks and ranks the issues.

  • XML, JSON, CSV, DMP, TXT
  • Flat files
  • File servers
  • System folders
  • Databases
  • Big-data stores
  • Enterprise systems
  • Social feeds

You decide: which sources go, and whether the validation report is clean enough to move on.

Transformation Agent

Reshapes your source data to fit the destination.

Proposes how each source attribute maps to the destination, applies the rules you choose, flags what it cannot map with confidence and re-validates the result.

  • Value changes
  • Merge and split
  • Enrich
  • Include or exclude
  • Filters
  • Custom program

You decide: every map and rule before it runs, and every flag it raises.

Load Agent

Loads into the destination you chose.

Stages objects, relationships and file entries with matched file paths, runs loads in parallel, logs each one and restarts from the last good point after an error.

You decide: the test-load results, and the go-ahead for production.

Latest Projects
Data Migration
An Unavoidable Pain

Data Migration is challenging and exasperating. It is not uncommon for migration projects to throw plans out of gear. However it is inevitable for constantly changing organizations to migrate data irrespective of its complexities, risks and costs involved. Companies aspire a business-as-usual pain-free data migration strategy and execution.






Migration – Top Drivers

Typical needs for migration in Organizations

Need for Migrations could result from various causes in an organization, It can be due to application modernization, mergers and acquisition, implementing a new software or integration of two systems, migration to cloud or regulatory mandates. No matter what the reason is an effective strategy and proven platform becomes imperative in the whole journey.



Migration Top Drivers

Data Migration – Typical Challenges & Pitfalls

Failure to follow Migration Best Practices & Use Standard Tools



Skipping Data Discovery & Due Diligence

  • Incomplete Data profiling of the source and target systems

Improper Audit, Validation & Data Quality Check

  • Missing Volume reconciliation, Pre & Post Extraction / Transformation & Load sampling

Underestimating Connectivity & Data Adapters

  • Lack of adequate Source and Target System adapters API compilations for extraction/loading
Data Migration


Inadequate Tools

  • Missing error / recover modules, file & data transforming handlers, flexible mappers, loggers and more

Lack of Cutover & Legacy Retirement Strategies

  • Missing legacy Retirement / Integration and system cutover planning.

Lack of Collaboration

  • Between Data Stewards, developers, business users, quality engineers
Albatross - A free ETL Data Migration Platform
A Extract Transform Load (ETL) based migration platform for Business critical & Large Migrations, Done Right, On Time.
Albatross Loader

Albatross Brochure Download

Albatross can extract, transform, validate and load data from most IT systems, artifacts, processes and stands strong with several man years of migration experience as its foundation.
Albatross provides modules that help reduce typical technical pitfalls in a migration project. A few of them include validation/resumption at each step of the migration de-risking the whole engagement. Flexible adapter framework that can extract or load data from simple files to complex databases or online feeds. A robust and blazingly fast File transfer module with pause - resume - restart capabilities.
Data transformation module that allows simple to complex mapping configurations thereby eliminating complex programming. Loading Parallelization that enables multifold reduction in the time taken for data loading. Coupled with migration best practices on the execution methodology, Albatross helps achieve successful migration time and again.

Albatross GIDX Payload Structure

Albatross GIDX



General Integration Data eXchange (GIDX)

General Integration Data eXchange (GIDX) is the platform’s neutral payload format that can transfer custom data over-the-wire for an effective data exchange between systems. The payload backbone handles custom data types, attributes, relations, relation attributes, files and formats, transformations and character encoding definitions.



ALBATROSS ARCHITECTURE

This is the engine the three agents drive: extraction adapters on the left, the validation and transformation engine in the middle, the loader on the right, with the GIDX payload underneath.

Albatross Architecture

Albatross Migrator Modules

Seven modules, each with an agent at its side. The agent does the repetitive part and shows you what it did; the module keeps every setting in your hands.

  • Albatross - Data Extractor

    Data Extractor

    • Adapter Connections

    • System Folders

    • File Servers

    • Databases

    • Social Feed

    • File Formats

    • Volume and Extraction Logs
    Extraction Agent: finds and connects to your sources, and reports volumes and logs before the first record moves.
  • Albatross - Pre-Migrate Validator

    Pre-Migrate Validator

    • Validation Algorithms
    • Post to Falcon Analytics Server
    • Load Analytics Report
      • File Missing
      • Missing Reference
      • Older Version
      • Data Type Mismatch
      • Format Check
      • Special Character
      • Duplicates
      • Missing Attributes
    Extraction Agent: runs the checks, groups the issues and ranks them, so your team fixes the worst first.
  • Albatross - xCAD Transformer

    xCAD Transformer

    • Validation Choices

    • Apply Transformation

    • Generate Transformed Data

    • Transformation Logs

    Transformation Agent: applies the transformations you chose and logs each change it makes.
  • Albatross - Post-Transform Validator

    Post-Transform Validator

    • Validation Algorithms
    • Post to Falcon Analytics Server
    • Load Analytics Report
      • Re-referencing
      • Correlated Reference
      • Latest Version
      • Data Type Mapped
      • Format Check
      • Special Characters
      • Duplicates Removed
      • Missing Attributes
    Transformation Agent: compares the result with the pre-migration report and points to what changed.
  • Albatross - Meta-Data Transformer

    Meta-Data Transformer

    • Data Mapper Configuration

    • Transformation Rules Sync

    • Destination Format/Size Validation

      • Plain/Value

      • Inclusion/Exclusion

      • Merge/Split

      • Enrich

      • Custom Program

      • Filters

    Transformation Agent: suggests source-to-destination attribute maps; you approve or edit each one.
  • Albatross - Loader Configurator

    Loader Configurator

    • Stage Load Settings
    • Error – Restart Config
    • Parallel loading Config
    • Loading Log Settings
    • Destination Adapter Connection Settings
    Load Agent: proposes stage, parallel and restart settings for your destination; you confirm them.
  • Albatross - Loader

    Loader

    • Stage & Run Load

    • Parallel Execution

    • Loader Logs

    • Error & Restart Load

    Load Agent: runs the load, logs it, restarts from the last good point after an error, and hands you the reconciliation.
  • Albatross - Your sign-off

    Your Sign-off

    • Approve the validation report
    • Approve maps and rules
    • Accept the test load
    • Release the production load
    You: the agents stop and wait at each of these points. Nothing moves to production until your data owners sign off.

Albatross Platform Gallery

Data Migration in Action

Albatross follows an ETL migration mechanism with configurability at every step. All steps are discrete and can be performed re-starting at a point where it was left off previously. Logs and notifications are generated at each module for validation and resumption.

Migration Module

Inside steps 5 and 6

One run through the Albatross Migrator

Each test round in the 7 steps of migration, and the production run after it, goes through these screens. An agent works each screen; your team clears it before the next.

  1. Choose source

    Extraction Agent
    Connects to your source and destination and lists what it found.You: confirm the scope

  2. Pre-migration validation

    Extraction Agent
    Runs the validation set and ranks issues: missing files, references, duplicates, format errors.You: accept the report

  3. Transformation

    Transformation Agent
    Proposes attribute maps and applies the rules you picked.You: approve the maps

  4. Validate transformation

    Transformation Agent
    Compares the result with the pre-migration picture and points to every difference.You: clear the flags

  5. Staging

    Load Agent
    Generates the stage files for objects, relationships and file entries.You: check the stage

  6. Loader settings

    Load Agent
    Proposes add, modify, delete or replace modes, parallel runs and restart points.You: confirm the settings

  7. Import

    Load Agent
    Loads, logs and reconciles; after an error it resumes from the last good point.You: sign off the load

The screens below show this run in the Albatross Migrator.

Loading Source & Extractor Connections

01Loading Source & Extractor Connections

- Choose Source System.
- Choose Destination System.
- Point to Workspace Directory
- Indicate Transformation Directory.
- Data Mapping Source Attributes.

Pre - Migration Validation

02Pre - Migration Validation

- Validation Set Choice.
- Execute Validator.
- Generate Analytics
- Post it to Crius Falcon Analytics Server.
- Launch Pre-Migration Validation Analysis.

Albatross Validation Analytics

03Albatross Validation Analytics

Configurable Dashboard to display data aggregates prior to and post transformation

Transformation (xCAD only)

04Transformation (xCAD only)

- File Open issues.
- Missing References.
- Data Type Mismatch and Format changes.
- Duplicates & Missing Attributes.
- Special character changes.

Post - Migration Validation (Compare Results with Pre-Validation)

05Post - Migration Validation (Compare Results with Pre-Validation)

- Validation Set Choice.
- Execute Validator.
- Generate Analytics.
- Post it to Crius Falcon Analytics Server.
- Launch Pre-Migration Validation Analysis.

Meta-Data Transformation

06Meta-Data Transformation

Data Transformation Mapper for Custom Attribute Settings on variations between Source and Destination Systems
Transformation Options -
- Attribute transformations can be simple value changes to split and merge. Complicated transformations can be achieved with Custom Program Plug-In with fuzzy mapper logic.
Transformation Mapper -
- Configurable mapper for various combinations of meta-data transfer provides clutter transformations in data and formats.

Loading Stage File Generator

07Loading Stage File Generator

- CSV based objects, relationships and file entries.
- Physical file paths correlated for check-in.

Loader Configurator

08Loader Configurator

- Add / Mod / Delete / Replace modes.
- Log and Notification settings.
- Error and Resume settings.
- Loader parallelization.
- Command Line syntax for App extension.

How do we plan and execute your migration?

The 7 steps of migration

Four phases, seven steps of migration. Step 6 is a test loop you repeat until the results match, then run once more on production. In each phase the agents prepare, check and report; your team signs off before the next phase starts.

The 7 steps of migration in four phases. Due diligence and planning: 1 study the source systems, 2 define checks and business rules, 3 define the ETL schema maps, 4 agree the migration plan. Develop and test: 5 extend the extractor and loader, 6 configure mapping and target, then test in a loop (extract, pre-validate, report conflicts, load, post-validate and compare, fix and add rules, stakeholder sign-off) until the results match. Production migration: step 6 on production (confirm readiness, configure, migrate, validate and accept). Monitor and support: 7 monitor and refine. Plan, test and acceptance sign-offs between phases; then integrate with Mateos.

Albatross and Pragmatos

Move off the old system, land on one you can grow

Your process may run on Excel, paper, someone's head, or a legacy system that does not fit the modern digital highway. Migrate with Albatross, build what replaces it on Helios, and integrate it with the rest of your plant through Mateos, all on Pragmatos.

1. Migrate with Albatross

The three agents carry your records, files and their relationships out of the old system, with a sign-off at every gate.

See the agents

2. Build it on Helios

The apps you build on Helios, and Flow on Pragmatos, are destinations the Load Agent can load into.

Build with Helios

3. Integrate with Mateos

After cut-over, Mateos keeps the new system in step with your ERP, MES and quality systems, so the data you moved stays current.

Integrate with Mateos

Pragmatos runs on prem, in your own cloud, or both. See Pragmatos

Illustrative Case Studies

Industry Equipment
Industry Equipment

Mining and Cement

  • Complex Migration of 4 systems to ENOVIA PLM
  • CAD and Meta-Data defining core product structures
  • Transformation, Validation Metrics and Reports
More
A & D Giant
A & D Giant

Migration/Integration

  • CATIA , ENOVIA, WINDCHILL triangular migration & integration
  • EPDM ERP Migration
More
Helios
Helios

Crius Rapid Application Development Platform

  • Crius Helios application development platform uses Albatross for all data migration needs
More
Aerospace Giant
Aerospace Giant

Migration/Integration

  • ENOVIA & Teamcenter
  • Migration & Integration
  • Visualization & Dashboards
More
PLM Implementation
PLM Implementation

End-to-End

  • Merger & Acquisition process
  • Smoothened for onboarding
More
Defense Giant
Defense Giant

Migration/Integration

  • 72+ systems & processes
  • Transformation ongoing for entire organization
  • Planned 9+ year engagement
Ozone
Ozone

Post-Migration Live Integration

  • Crius Compliance Engine Ozone uses Albatross data migrator for transferring BOM, Parts, Vendors, Material and Substance information and Mateos® for Integration post migration
More
FAQ
Migration engagements is specific to any customer, environment and dataset? How does Albatross handle these variations?
Albatross platform provides the core modules that are typically needed in a migration project. It includes standard templates for data extraction, interface adapters, error handling and resumption, data transformation module to fit the destination system, standard loading templates for objects/relations/files, loader configuration settings, loader adapters, logging and notification core, file transfer modules and more. These form a bulk of any migration engagement. The variations on the source and destination systems are handled by the adapter functions that is implemented during the migration project.
What makes Albatross so advanced?
The extraction, validation, transformation and load modules are connected by simple and specific data formats. These modules can be used as a standalone or can be skipped based on the needs of the project. This allows validation/resumption at each step of the project de-risking the whole engagement. Flexible adapters can connect for data extraction from simple files to complex databases or online feeds. File transfer module is robust and blazingly fast with pause/resume/restart capabilities. Data transformation module allows simple mapping configurations thereby eliminating complex programming. With Parallelization, data loading is reduced multifold.
How will Albatross help in my migration implementation?
The platform is a by-product of years of migration experience. Most of the technical migration project pitfalls have been addressed in the platform. Crius has been able to de-risk migration projects that are typically complex with Albatross. Flexible adapter plug in framework, File Transfer Module, staging modules, data transformation engine, parallelization and other features prevents typical migration technical failures.
Does Crius have an implementation methodology?
We follow a iterative V model for migration sampling and testing the system de-risking at the earlier stages of the engagement itself.

Subscribe to our newsletter

Subscribe to get notified about latest updates on Crius.