Vendor Lock-In Risk Assessment (Onboarding)

Vendor Lock-In Risk Assessment (Onboarding)

1. 01

   Inventory the data engineering tools proposed for the client pipeline

   List every platform in the stack, from ingestion to transformation to orchestration, and note whether each is proprietary, open-source, or a managed service.

2. 02

   Classify each tool by its portability profile

   For each tool, determine if the data models, transformations, and orchestration logic can be exported in standard formats (SQL, Python, DAG definitions) or if they are locked into vendor-specific abstractions.

3. 03

   Assess the client's stated preference for open-source or customizable pipelines

   Review the contract and discovery notes. If the client explicitly requires open-source components or the ability to self-host, flag any proprietary automation that would violate that requirement.

4. 04

   Estimate the migration cost if the client switches tools mid-engagement

   Calculate the effort to re-implement pipelines in an alternative tool, including data extraction, transformation logic, and orchestration rewrites. Use a rough day estimate per pipeline to quantify the risk.

5. 05

   Check the vendor's data export and API access capabilities

   Verify that the tool provides full data export, API access to metadata, and the ability to extract transformation logic. If the vendor restricts export, document that as a high-risk lock-in factor.

6. 06

   Review the contract for exit clauses and data portability guarantees

   Look for terms that allow the client to retrieve all data and configurations upon termination. Note any penalties or restrictions that would make switching prohibitively expensive.

7. 07

   Document the lock-in risk rating and present it to the client

   Summarize the findings in a risk register, rating each tool as low, medium, or high risk. Include a recommendation on whether to proceed, mitigate, or require a different tool.