ss5-data-migration

Automate Silverstripe 4 to Silverstripe 5 data migration via slash commands.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/muskie9/agents --skill ss5-data-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss5-data-migration
Source: https://github.com/muskie9/agents/tree/main/skills/ss5-data-migration
Command: npx skills add https://github.com/muskie9/agents --skill ss5-data-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires silverstripe, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the workflow for executing data migration tasks after upgrading a Silverstripe 4 project to Silverstripe 5, ensuring all data is properly migrated.

Core Features & Use Cases

  • Data Migration Workflow: Provides a structured sequence of tasks for migrating layout, content, and settings data.
  • Project-Specific Migration: Offers guidance on formalizing a project-specific migration command.
  • Automated Execution: Executes all tasks automatically through a slash command or a script runner.
  • Deployment Strategy: Suggests a deployment strategy for migrated data and pre-computed assets.
  • Heuristic Link Verification: Ensures links remain functional after structural changes.
  • Troubleshooting Guide: Offers troubleshooting steps for common issues during the migration process.

Quick Start

Run the /migrate slash command or migrate.sh script to execute the full SS5 data migration for your project after a fresh production database sync.

Frequently Asked Questions about ss5-data-migration

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

FAQPage Schema
How do I automate Silverstripe 5 data migration after a project upgrade?

Silverstripe 5 data migration can be automated by running the `/migrate` slash command or `migrate.sh` script, which executes a structured sequence of tasks to migrate layout, content, and settings data from a Silverstripe 4 project.

What is the process for migrating SS4 project data to Silverstripe 5?

Migrating SS4 project data to Silverstripe 5 involves executing a structured workflow of tasks that transfer layout, content, and settings, while formalizing a project-specific migration command to ensure all data is properly migrated and links remain functional.

Do I need a fresh production database sync before starting SS5 data migration?

Yes, a fresh production database sync is required before starting SS5 data migration to ensure data integrity, as the automated execution processes the full migration sequence against the current production state of your Silverstripe project.

How do I verify links remain functional after a Silverstripe 5 data migration?

To verify links remain functional after Silverstripe 5 data migration, the process includes heuristic link verification, which checks that links stay intact following structural changes made during the layout, content, and settings data transfer.

What's the best way to troubleshoot common issues during SS5 data migration?

The best way to troubleshoot SS5 data migration issues is to follow the included troubleshooting guide, which provides specific steps to resolve common problems that occur while migrating project data and pre-computed assets.

Can I define a project-specific migration strategy for Silverstripe 5?

Yes, you can define a project-specific migration strategy for Silverstripe 5, as the workflow offers guidance on formalizing a custom migration command tailored to your project's unique layout, content, and settings requirements.