The document outlines the migration process to Magnolia version 4.5, detailing challenges faced by the Namics AG team, including performance issues and the inadequacies of the initial migration module 1.1. It emphasizes the improvements made in migration module 1.2, which enhanced automation and documentation but also notes the complexities and time overruns experienced during the project. Key recommendations include thorough preparation, utilizing updated migration tools, and allowing sufficient time for the migration process.

3. DANIEL KUMMER. Senior Software Engineer.
STEFAN BAUR. Software Engineer.
Namics AG
September 2013

5. MIGRATION
PROCESS
THE ROAD TO 4.5

11. PROJECT
DATA
C O N T E X T
customer
magnolia
balôise group
internet (2010)
intranet (2011)
enterprise edition
ldap
shop
weblogic
modules
sites

12. PROJECT
DATA
N U M B E R S
4.4.9-jcr2
1
5
~25GB
~30’000
~130
~50
~50
3
pre-migration version
author (production)
publish (production)
repository size
content pages
custom components
custom pages
site definitions
custom themes

14. FIRST
ATTEMPTS
STILL PREMATURE
we expected it to be a big help - but it wasn’t
groovy scripts - impossible to debug errors
premature documentation
started migrating code - while waiting for magnolia
MIGRATION
MODULE 1.1

15. FINAL
SOLUTION
NEW AND POLISHED!
MIGRATION
MODULE 1.2
CHANGES…
every module migrates itself
no more groovy scripts à replaced with tasks
excellent automatic migration of freemarker scripts
overhauled and improved documentation

16. FINAL
SOLUTION
NEW AND POLISHED!
MIGRATION
MODULE 1.2
…AND ISSUES
poor performance à complete migration: ~100h!
some dependent modules still used 1.1 {form, shop}
still some unpleasant bugs

18. POST
MIGRATION
DONE? WRONG!
MAGNOLIA
4.5 PITFALLS
lots of templating changes
complex area migration
performance issues with “old” 4.4 code
bugs in the early magnolia 4.5.x releases

19. POST
MIGRATION
THE NEW STUFF
BIGGEST 4.5
CHANGES
templating à stk 2.0
area concept
renderable definitions
inplace editing
jcr node api
ldap/ad module
channels

21. ESTIMATES
R E A L I T Y
~35 days
~100 days
3x
OFF

22. WHY
???
REASONS
one of the first large migrations
no reference estimations
migration module 1.1 unusable
unexpected post migration issues
complex custom code migration
more testing than estimated

23. O U R
T I P S
GET IT DONE RIGHT
read the wikis – read them well
take your time – don’t hustle
use content migration tasks
estimate conservative
migration module 1.2 is your friend

25. ?
QUESTIONS