PHPackages                             sbuerk/dce-fce-migration - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. sbuerk/dce-fce-migration

ActiveTypo3-cms-extension[Utility &amp; Helpers](/categories/utility)

sbuerk/dce-fce-migration
========================

Specialist dce to fce migration toolchain

0.0.7(3y ago)1104GPL-2.0-or-laterPHPPHP ^7.2

Since Aug 18Pushed 3y ago1 watchersCompare

[ Source](https://github.com/sbuerk/dce-fce-migration)[ Packagist](https://packagist.org/packages/sbuerk/dce-fce-migration)[ RSS](/packages/sbuerk-dce-fce-migration/feed)WikiDiscussions main Synced today

READMEChangelogDependencies (6)Versions (8)Used By (0)

DCE to FCE Migration Toolchain
==============================

[](#dce-to-fce-migration-toolchain)

Introduction
============

[](#introduction)

This package contains a toolchain for migration DCE to FCE in several (internal/customer) projects. It contain's only the stuff we needed so far, so this is not a full-fledged feature enriched package, and maybe will never become one. Feel free to fork and extend it with the things you need.

Installation
------------

[](#installation)

This package is currently only available as composer package.

```
$ composer require sbuerk/dce-fce-migration
```

Usage
-----

[](#usage)

This package comes with a centralized command to process migrations. However, migrations are project specific and thus must be provided by the instance. They must be registered, so the command can pick them up.

### Command Usage

[](#command-usage)

```
$ vendor/bin/typo3 dce2fce:migrate              # list migrations
$ vendor/bin/typo3 dce2fce:migrate --run        # run all registered migrations
$ vendor/bin/typo3 dce2fce:migrate --run \      # run only selected migration(s)
  --select="dce-1" --select="dce-2"             # using the select option to select by identifiers
```

Migrations are registered with the global `$GLOBALS['DCE_FCE_MIGRATIONS']`:

```
$GLOBALS['DCE_FCE_MIGRATIONS'] = array_replace(
    $GLOBALS['DCE_FCE_MIGRATIONS'] ?? [],
    // register migrations
    \Vendor\Extension\Migrations\YourDceElementMigrationClass::class,
);
```

TODO's
------

[](#todos)

\[ \] Enrich README.md with information about how to write custom DCE-&gt;FCE Migration sets \[ \] Explain basic migration sets templates \[ \] Add tests to cover the functionality

Tagging and releasing
---------------------

[](#tagging-and-releasing)

packagist.org is enabled via the casual github hook. TER releases are created by the "publish.yml" github workflow when tagging versions using tailor. The commit message of the tagged commit is used as TER upload comment.

> @todo TER Release not implemented yet

Example:

```
composer install
.Build/bin/tailor set-version 0.2.0 --no-docs
git commit -am "[RELEASE] 0.2.0 Bug fixes and improved core v11 compatibility"
git tag 0.2.0
git push
git push --tags
```

###  Health Score

20

—

LowBetter than 13% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity11

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity37

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~16 days

Recently: every ~24 days

Total

7

Last Release

1318d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/1453466?v=4)[Stefan Bürk](/maintainers/sbuerk)[@sbuerk](https://github.com/sbuerk)

---

Top Contributors

[![sbuerk](https://avatars.githubusercontent.com/u/1453466?v=4)](https://github.com/sbuerk "sbuerk (16 commits)")

### Embed Badge

![Health badge](/badges/sbuerk-dce-fce-migration/health.svg)

```
[![Health](https://phpackages.com/badges/sbuerk-dce-fce-migration/health.svg)](https://phpackages.com/packages/sbuerk-dce-fce-migration)
```

###  Alternatives

[friendsoftypo3/content-blocks

TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML

103519.9k53](/packages/friendsoftypo3-content-blocks)[wazum/sluggi

TYPO3 extension for URL slug management with inline editing, auto-sync, locking, access control, and redirects

40529.5k](/packages/wazum-sluggi)[typo3/cms-scheduler

TYPO3 CMS Scheduler - Schedule tasks to run once or periodically at a specific time.

169.3M231](/packages/typo3-cms-scheduler)[typo3/cms-lowlevel

TYPO3 CMS Lowlevel - Technical analysis of the system. This includes raw database search, checking relations, counting pages and records etc.

178.2M315](/packages/typo3-cms-lowlevel)[typo3/cms-redirects

TYPO3 CMS Redirects - Create manual redirects, list existing redirects and automatically createredirects on slug changes.

167.4M80](/packages/typo3-cms-redirects)[typo3/cms-form

TYPO3 CMS Form - Flexible TYPO3 frontend form framework that comes with a backend editor interface.

147.6M264](/packages/typo3-cms-form)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
