Value Proposition

As part of the complete assessment process, the insights produced help in many ways. Let us see the value it creates in knowing the starting point for your migration. It helps create a phase-wise, prioritized blueprint of your migration plan. This strategizes your offload program based on data-driven analysis and insights. Hence, it identifies and mitigates migration risks beforehand by itself. Let’s have a look at some more details on the value it brings to the table.

Insights	Value and Benefits
Complete source inventory Queries Procedures Functions Views Packages ETL scripts and their contents	The quantum of inventory needs to be scoped for migration. Count of queries, procedures, functions, views, packages, etc. running in a typical enterprise data warehouse environment. Informatica: Workflows, mappings, sessions, expressions, source queries, procedure blocks, etc. DataStage: File-wise jobs, activities, stages, transformations, and job-level information. Ab Initio: File-wise components, input/output sources, and other components such as Transform, Metadata, Inout, Flow, etc.
Code complexity	Understand existing complexity landscape and estimate conversion effort.
Conversion/Transformation	Generates important insights relating to: The quantum of auto-convertible code. Parsable and unparsable code: Highlights the quantum of work in terms of a total count of queries, procedures, functions, etc. Dead code i.e., completely unused code. Whether the pattern occurring in the code is supported or not. Re-engineering candidates etc. Certain queries specifically designed according to source-specific nuances may need to be completely re-engineered or refactored as per the chosen target. The logic of such queries is typically too complex, resource-constraining, and cost-incurring on the source and hence needs complete refactoring. Missing and additional artifacts. Missing artifacts, for example, a KSH script is referred to in an Informatica job but is not supplied in the input. Additional artifacts, for example, some additional artifacts are coming which has no reference in the input artifacts.
Dependency structure: end-to-end lineage Triggering orchestration scripts Participating scripts Input and output tables Orchestration sequence	Identify the phase-wise scope for migration by dividing migration into separate logical units. Sprint planning
Optimization Schema Orchestration	Schema optimization opportunities: Partitioning, Bucketing, Clustering strategy. Orchestration optimization opportunities: Identify parallel orchestration opportunities.