migration-strategies

Implements data, API, and system migration patterns with rollback and compatibility strategies.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/Dazlarus/karl-code --skill migration-strategies-dazlarus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-strategies
Source: https://github.com/Dazlarus/karl-code/tree/main/.agents/skills/migration-strategies
Command: npx skills add https://github.com/Dazlarus/karl-code --skill migration-strategies-dazlarus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving data, APIs, or entire systems to new platforms without breaking existing clients or losing data is risky and complex. This Skill provides proven patterns for planning and executing migrations safely, including gradual cutover, backward compatibility, and rollback procedures. ## Core Features & Use Cases - Strangler Fig Pattern: Gradually route traffic from legacy services to new implementations using percentage-based routing. - Batch Data Migration Pipelines: Migrate records in configurable batches with transform functions and failure tracking. - API Versioning & Proxying: Run old and new API endpoints side by side, migrating users on access while maintaining backward-compatible response formats. - Rollback Planning: Wrap migrations in forward/backward callable pairs so failed migrations can be reverted cleanly. - Use Case: When moving a user database from a legacy SQL system to a new document store, use the DataMigrator pattern to batch-transform records, proxy API requests during the transition, and keep a rollback path ready. ## Quick Start Ask the agent to design a zero-downtime migration plan for moving your user data from a legacy database to a new system with rollback support.

Frequently Asked Questions about migration-strategies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate data between databases without downtime?▼

Use a batch data migration pipeline that fetches records from the source in configurable batch sizes, transforms each record, and writes to the destination. Combine this with a proxy layer that routes reads to whichever system holds the data during the transition.

What is the strangler fig pattern for system migration?▼

The strangler fig pattern gradually replaces a legacy system by routing a percentage of requests to the new implementation while the rest still hit the old one. You increase the migration percentage over time until the legacy system can be retired.

How do I keep an API backward compatible during migration?▼

Run versioned endpoints side by side and add a proxy endpoint that routes to the appropriate version, migrating users on access. A compatibility service can also transform new-format responses back into the legacy field structure for old clients.

How do I roll back a failed data migration?▼

Wrap the migration in forward and backward callables: execute the forward migration, and if it fails, invoke the backward callable to restore from backup. Always take a backup before starting and track whether the migration completed.

When should I not use these migration patterns?▼

For simple schema updates, use a dedicated database-migrations approach instead, and for plain database queries use a query-focused tool. These patterns are intended for cross-system, API, or large data migrations, not routine schema tweaks.