Cloud Migration Glossary
Understand the technical and business terminology you need to fully plan and action your migration to the cloud.
Application Migration
The migration of tools and applications that use the source database such as BI reports and custom apps to now use the target cloud database.
This may consist of:
- A simple re-configuration of the affected tools and applications
- The migration of a newer version of the application if changes were required
Application Subject Matter Experts
Offer insight on the applications deployed within the legacy system.
Business Consumer Subject Matter Experts
Answer questions on data consumption patterns on behalf of business users.
Chief Architect
Lead migration workshops and review deliverables related to the migration solution architecture and methodology.
Data Analyst
Answer data related questions about the legacy environment and its consumption patterns.
Data Migration
This includes the migration of historical data from source database tables to the cloud target and materializing associated data in views and indexes.
Data Pipeline Migration
The migration of data processing logic from the source environment to equivalent data processing logic in the target cloud environment.
Source data processing logic often takes the form of:
- Database scripts
- ETL tool pipelines
- Shell scripts and applications and more
Database Management Migration
The migration of administrative and operational utilities and functions from the source database to the target cloud environment.
This often includes the migration of:
- Job schedules
- Administrative processes such as backups and reorgs
- Database management tool configurations
- Utility “scripts” and more
Legacy Architect
Provide legacy architectural documentation and address questions about the legacy environment.
Metadata Migration
The migration of business, technical and operational metadata from the source environment to the target cloud environment as well as any mappings or link-ages between them.
This metadata is commonly stored in distinct source repositories separate from the main source database.
Program Manager
Remove migration blockers and coordinate resources on behalf of the team.
QA Lead
Lead QA team, and interface with Migration QA Lead, throughout the QA and Testing Phase.
QA Testers
Perform user-acceptance and business-acceptance testing during the QA and Testing Phase.
Schema Migration
This phase focuses on the migration of source database objects to equivalent objects of the target environment.
Legacy database object types vary but typically include:
- Tables and views
- Indexes, synonyms and sequences
- Stored functions
- Procedures, packages, triggers and more
Security Migration
The migration of database security objects and properties to equivalent objects in the target cloud environment.
Security objects and properties vary from one database environment to another but typically include:
- User accounts roles and permissions
- User-profiles and limits
Target Environment Architect
Address architecture, environment and infrastructure questions related to the target cloud environment.
Target Environment Technical Lead
Share knowledge on the performance, capacity & configurations related to the cloud environment relative to the legacy system.
Technical Manager
Validate technical solutions, approaches, designs and address technical issues that come up in the migration project.
