boilerplate extension for upgrading TYPO3 6.2 to 8.7
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

This extension is a boilerplate to organize all necessary upgrade steps to bring TYPO3 Installations from 6.2 to 8.7. Thanks to Helmut Hummel for his great EXT:typo3_console, which is heavily used here.

Beware: this is ONLY A BOILERPLATE which needs individual adaptions for each projects.

Basically - if you did all the adaptions - you can then just run a bash script to do the complete upgrade.

bash ./web/typo3conf/ext/upgrader/6to8/ -d dbdump.sql -s keyForCurrentMachine

Script Parameters:

-d (relative) path to your DB dump
-s Key for machine environment (like devFranz): This is used currently in the naming of some sql-command-files to allow different things on different machines.
-p path to your project root, if you want to bring that in as parameter

You can use the script to run firstly several times on your dev machine until all looks good, then on the staging maschine, and finally for the live upgrade, where you can be pretty sure that all will work well (and fast).

The Xclasses are there to avoid that the upgrade script dies just because of problematic data in DB. We try to catch such exceptions and write them to a log file.

Questions and answers

We welcome pull requests also for this little documentation, if you have questions or experiences you want to share.

Is it only useful for upgrading from 6 to 8?

Basically it should also work for 7 to 8, we work on those currently. Probalby even for upgrades to 9. Stay tuned.

What about upgrading from 4.5?

We did not try integrating necessary steps for upgrading from 4.5. Since we run the script only from within a working TYPO3 8 with PHP7, we would expect some problems with the upgrade-wizards in 6.2. Especially the FAL-Migration is a huge task there. We are willing to do some evaluation and try to find solutions there if enough people are in need of this step and we can raise enough funds.
If you already have scripted solutions for this step, we appreciate pull requests.

How is the best procedure for organizing an upgrade with this extension

Here is how we suggest to do it right now:

  • Clone your existing project (new DB, new folder)
  • leave DB-dump for later use, you will probably have to run the script several times until all is fine
  • uninstall all local extensions (from typo3conf/ext)
  • switch to TYPO8 (i.e. by symlinking the new core or by creating a new empty project)
  • upgrade and install all local extensions to versions which are compatible to 8
  • install EXT:upgrader
  • work through what you need to change in your specific project for it to run smoothly in 8. See sql-files in folder 6to8/sql/projectspecific to get some ideas. We plan to add more examples from what we had to do in different projects to give more ideas how things can be done.
  • run the migration with the original sql dump (so far we never needed to set back the filestructure i.e. in fileadmin, no changes there - you could do that with rsync if needed)
  • fix what went wrong and re-run the script, again with the original sql dump