cfmigrations

Create and apply versioned database migrations for ColdBox/BoxLang projects.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ColdBox/skills --skill cfmigrations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cfmigrations
Source: https://github.com/ColdBox/skills/tree/main/modules/cfmigrations
Command: npx skills add https://github.com/ColdBox/skills --skill cfmigrations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage database schema changes in ColdBox/BoxLang by using cfmigrations and its Schema Builder to version and apply migrations, including seed data for development and testing.

Core Features & Use Cases

  • Migration file structure with up() and down() methods to apply and rollback changes
  • Schema Builder API to create, alter, drop tables, columns, indexes, and foreign keys
  • Seed files to populate development and test data
  • CLI integration with commands like migrate create, migrate up, migrate down, migrate status
  • Grammar support for multiple SQL dialects and safe rollback workflows

Quick Start

Create your first migration file with migrate create and then apply pending migrations with migrate up

Frequently Asked Questions about cfmigrations

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

FAQPage Schema
How do I manage database schema changes in ColdBox or BoxLang applications?

You manage database schema changes in ColdBox and BoxLang by using versioned database migrations with the cfmigrations library, which tracks schema state and applies structural updates systematically.

How do I create and run database migrations using CommandBox CLI?

You create migration files with the 'migrate create' command and apply pending schema changes using 'migrate up' via CommandBox CLI to automate deployment pipelines and keep environments synchronized.

Can I rollback database schema changes if a migration fails in ColdBox?

Yes, cfmigrations enforces up() and down() migration semantics, allowing you to safely rollback applied schema changes using the 'migrate down' command to revert to a previous database state.

What is the best way to populate test data in a ColdBox database migration workflow?

The best way to populate test data in ColdBox is by using cfmigrations seed files, which insert specific development and testing datasets into your database after the schema migrations are applied.

Does cfmigrations support multiple SQL dialects for ColdBox schema management?

Yes, cfmigrations supports multiple SQL grammars, allowing the Schema Builder to generate the correct SQL dialect for your specific database engine during migration execution.

Do I need CommandBox to use cfmigrations for database versioning?

CommandBox CLI is required for automated deployment pipelines and running migration commands like 'migrate status', but the Schema Builder API itself handles the core database versioning logic within your ColdBox application.