Skip to content

Legacy Migration Basic Concepts

Introduction

Legacy migration refers to the process of transferring data, processes, and workflows from our old system to a new and more efficient Enterprise Resource Management System (ERM).

Terminologies

Account

  • An account is an identity used to grant access to a system. It serves as the basis for all permissions and access control in the system, and it is identified by an email address.
  • The email address is part of the notification workflow for example password reset
  • Overall, the account is a crucial component of any system, and it plays a central role in managing access, authentication, and user information

Legacy VS ERM

  • The legacy system — Previous database system
  • ERM (Enterprise Resource Management) — Current database system

Non-Repudiation Concept

This is a security concept that ensures that a party cannot deny or repudiate the actions or transactions they have taken in a system.

Certain actions for example code generation must be traced without any possible repudiation.

Delegation of Service

This refers to the process of assigning or transferring specific tasks, duties, or responsibilities from one individual or group to another individual or third party.

Product Assignment

This is linking individual products to a fleet and assigning that fleet to an account or user.

Three layer concept:

  • Products
  • Fleet
  • Account

Relationship

There is a one-to-many relationship for the above. The one-to-many relationship between these layers means that an account can have many fleets, and a fleet can have many products.

A product is assigned to a fleet and in turn a fleet is assigned to account.

API vs UI

  • API — Calling either the GraphQL or legacy REST API directly
  • UI — The ERM dashboard

Same Endpoints

Both API and UI have the same API endpoints.