This document discusses strategies for migrating a Plone site from one version to another. It recommends a step-by-step process of first cleaning up the site, then migrating linguaplone, upgrading to Plone 5, migrating to Dexterity, migrating to Python 3, and finally cleaning up again. Resources provided include links to documentation and code on GitHub for automating parts of the migration process.

1. MIGRATIONSMIGRATIONSMIGRATIONS
PHILIP BAUER
MIGRATIONS
MIGRATIONS
MIGRATIONSMIGRATIONS
MIGRATIONS
MIGRATIONSMIGRATIONSMIGRATIONS @StarzelDepbauer

2. PLONE 4 TO PLONE 5
LINGUAPLONE TO PAM
ARCHETYPES TO DEXTERITY
PYTHON 2 TO PYTHON 3

3. GITHUB.COM/COLLECTIVE/
COLLECTIVE.MIGRATIONHELPERS

4. AUTOMATE ALL THE THINGS

7. GET THE BIRDS-EYE VIEW

12. DIVIDE AND CONQUER

16. MAKE BIG PROBLEMS SMALL

18. DO NOT MIGRATE BLOBS

19. EXPERIMENTAL.GRACEFULBLOBMISSING

20. FORGET THE PAST

23. ADDONS

28. PROFILES

30. PERSISTENT $%*T

32. PATCH

36. LINGUAPLONE

38. https://github.com/collective/collective.migrationhelpers/
blob/master/src/collective/migrationhelpers/linguaplone.py

39. UPDATE TO PLONE 5.2

41. RTFM: HTTPS://DOCS.PLONE.ORG/MANAGE/
UPGRADING/VERSION_SPECIFIC_MIGRATION/
UPGRADE_TO_52.HTML

42. MIGRATE TO DEXTERITY

45. CUSTOM CONTENT

52. ALTERNATIVE 1: INPLACE
MIGRATOR FROM FTW.UPGRADE

53. ALTERNATIVE 2: REPLACE
OBJ BASE-CLASS

55. MIGRATE TO PYTHON 3

56. DB MIGRATION TO PY3

58. PACK DATABASE TO 0 DAYS

59. IGNORE ZODBVERIFY (MOSTLY)

60. ALIAS_MODULE IS YOUR FRIEND

62. CLEANUP (AGAIN)

64. FINALIZE

66. WHY DO IT THIS WAY?

67. GITHUB.COM/COLLECTIVE/
COLLECTIVE.MIGRATIONHELPERS

68. 1. CLEANUP
2. MIGRATE LINGUAPLONE
3. UPGRADE TO PLONE 5
4. MIGRATE TO DEXTERITY
5. MIGRATE TO PYTHON 3
6. CLEANUP

69. MIGRATE TO PLONE 6

70. THANKS
@StarzelDepbauer