block-to-element-migration

Migrate legacy SilverStripe blocks to Elemental with data and template mapping.

Updated Jun 18, 2026

Search Tags:#data migration #silverstripe #block migration #elemental #template parity

Ready to run

npx skills add https://github.com/muskie9/agents --skill block-to-element-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: block-to-element-migration
Source: https://github.com/muskie9/agents/tree/main/skills/block-to-element-migration
Command: npx skills add https://github.com/muskie9/agents --skill block-to-element-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires silverstripe/silverstripe-elemental, silverstripe/silverstripe-blocks, and includes scripts (resource) and references (resource) and examples (resource) components.

What problem does it solve?

This Skill automates the migration of legacy SilverStripe blocks to the modern Elemental system, streamlining the upgrade process from SS3 to SS4 or later versions.

Core Features & Use Cases

Legacy Block Mapping: Automatically maps legacy block classes to their corresponding Elemental elements.
Data Migration: Moves Block and SiteTree_Blocks data to Element, ElementContent, and related sub-objects.
Template Parity: Preserves the visual and functional parity of legacy block templates.
Use Case: If you're upgrading a SilverStripe 3 site to 4 and need to migrate existing blocks to the Elemental system, this Skill can help you do it efficiently.

Quick Start

Run the 'block-to-element-migration' skill to automatically convert all legacy blocks on your site to Elemental elements.

Frequently Asked Questions about block-to-element-migration

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

FAQPage Schema

How do I migrate SilverStripe blocks to Elemental during a CMS upgrade?▼

Migrating SilverStripe blocks to Elemental involves mapping legacy block classes to Element classes and moving SiteTree_Blocks data to Element objects. This Skill automates that data migration while preserving template parity.

What is the best way to keep SilverStripe block templates working after moving to Elemental?▼

Maintaining SilverStripe block templates during an Elemental migration requires achieving template parity between legacy blocks and new Elements. The migration process automatically maps and preserves the visual and functional parity of existing templates.

What versions of SilverStripe and Elemental do I need to run a block migration?▼

Running a block migration requires SilverStripe 3.4+ and the Elemental 3.4+ module. This process is specifically designed for sites upgrading from SilverStripe 3 to SilverStripe 4 or later versions.

Can I automatically map legacy block classes to Elemental elements in SilverStripe?▼

Automatically mapping legacy block classes to Elemental elements is a core feature of the block migration process. It maps existing blocks to corresponding Element and ElementContent sub-objects to streamline the CMS upgrade.

How does the SilverStripe block data migration process move SiteTree_Blocks records?▼

The SilverStripe block data migration process moves Block and SiteTree_Blocks records to Element and ElementContent objects. This ensures all legacy content is accurately transferred to the Elemental system structure.

Does the block to Elemental migration work for both SS3 to SS4 upgrades and later versions?▼

The block to Elemental migration works for SilverStripe 3 to 4 upgrades and later versions. It handles the complete transition of legacy block data and templates to the modern Elemental architecture.