silverstripe-3-to-4-upgrade

Migrate Silverstripe 3 projects to Silverstripe 4 with package and namespace updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires silverstripe/recipe-version-upgrade, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive upgrade path for legacy Silverstripe 3 projects to Silverstripe 4, ensuring seamless migration with parity, not redesign.

Core Features & Use Cases

  • Assessment: Identifies package differences, prepares for migration, and sets up a legacy instance.
  • Directory Structure: Renames mysite to app, introduces a public directory for assets and configuration.
  • Dependencies: Updates composer.json for compatibility with Silverstripe 4 and modern PHP requirements.
  • Namespacing: Implements PSR-4 autoloading and maps database class names to their new locations.
  • Database Schema: Resolves preflight issues like FULLTEXT indexes and table collisions.
  • Data Migration: Handles file migration, namespace migration, and custom SQL tasks.
  • Templates: Updates templates for Silverstripe 4 compatibility.
  • Build & Verify: Ensures the build process works correctly and performs frontend and admin QA.
  • Code Quality & CI: Enforces code quality with tools like PHPCS, PHPStan, and PHPUnit.

Quick Start

Run the silverstripe-3-to-4-upgrade skill to begin the upgrade process.

Frequently Asked Questions about silverstripe-3-to-4-upgrade

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

FAQPage Schema
How do I upgrade a legacy Silverstripe 3 project to Silverstripe 4?

Upgrading a legacy Silverstripe 3 project to Silverstripe 4 involves migrating package updates, namespaces, database schemas, and templates. This Skill automates the process to ensure migration parity rather than a full redesign.

What directory structure changes are required for Silverstripe 4 migration?

Silverstripe 4 migration requires renaming the `mysite` directory to `app` and introducing a new `public` directory for assets and configuration to align with modern framework standards.

How does the Silverstripe 4 upgrade handle database schema and namespacing?

The Silverstripe 4 upgrade resolves preflight database issues like FULLTEXT indexes and table collisions. It implements PSR-4 autoloading and maps legacy database class names to their new namespaced locations.

Do I need a working Silverstripe 3 instance to start the migration?

Yes, you need a working Silverstripe 3 instance and a development environment configured for Silverstripe 4. The migration process begins by assessing package differences and preparing a legacy instance.

What code quality tools are enforced after completing the Silverstripe migration?

After completing the Silverstripe migration, code quality is enforced using tools like PHPCS, PHPStan, and PHPUnit to ensure the upgraded project meets modern development standards.

Can I update templates and composer dependencies for Silverstripe 4 compatibility?

Yes, the upgrade process updates `composer.json` for compatibility with Silverstripe 4 and modern PHP requirements, while simultaneously adjusting existing templates to ensure full Silverstripe 4 compatibility.