Configuration Migration with Integrity Assurance

Problem/Feature Description

A platform engineering team is migrating critical service configuration values — API base URLs, rate limit thresholds, and feature flag states — from a legacy config file into a new key-value store that will be shared across microservices. The migration has to be safe: any silent data corruption during transfer would cause hard-to-debug production incidents.

The team wants a migration utility that transfers each configuration entry into the new store in a way that lets them prove the data arrived intact. If anything looks wrong after storage, the tool should make that visible immediately rather than letting corrupted config silently propagate. The final output should be a report that auditors can sign off on before the team promotes the new store to production.

Output Specification

Produce two files:

1. migrate_config.py — A Python script that writes each configuration entry below into an in-memory or file-based key-value store (using only Python standard library), performs an integrity check on each entry after writing, and prints a JSON report to stdout.

2. migration_report.json — The report produced by running the script. It must include, for each entry: whether the write succeeded, whether the stored data was verified, and a final classification. Also include an overall summary at the top level.

The script must be runnable with python migrate_config.py using only Python standard library modules.

Input Files

Migrate the following configuration entries:

[
  {"key": "payments_api_base_url", "value": "https://payments.internal.example.com/v2", "owner": "payments-team"},
  {"key": "rate_limit_requests_per_minute", "value": "300", "owner": "platform"},
  {"key": "feature_flag_new_checkout", "value": "enabled", "owner": "growth-team"},
  {"key": "db_connection_pool_size", "value": "20", "owner": "platform"}
]