Always make sure to backup your database before starting the upgrade process.
In a terminal, on the host where Twenty is running, turn off Twenty: docker compose down
Upgrade the version by changing the TAG
value in the .env file near your docker-compose.
Bring Twenty back online with docker-compose up -d
Migrating a CRM is a bit trickier than migrating a traditional software, because the data model of Standard Object has to evolve smoothly along your custom objects.
Run the following commands:
yarn database:migrate:prod
yarn command:prod workspace:sync-metadata -f
yarn command:prod upgrade-0.22
The yarn database:migrate:prod
command will apply the migrations to the Database.
The yarn command:prod workspace:sync-metadata -f
command will sync the definition of standard objects to the metadata tables and apply to required migrations to existing workspaces.
The yarn command:prod upgrade-0.22
command will apply specific data transformations to adapt to the new object defaultRequestInstrumentationOptions.
Run the following commands:
yarn database:migrate:prod
yarn command:prod upgrade-0.23
The yarn database:migrate:prod
command will apply the migrations to the Database.
The yarn command:prod upgrade-0.23
takes care of the data migration, including transferring activities to tasks/notes.
Run the following commands:
yarn database:migrate:prod
yarn command:prod upgrade-0.24
The yarn database:migrate:prod
command will apply the migrations to the database structure (core and metadata schemas)
The yarn command:prod upgrade-0.24
takes care of the data migration of all workspaces.
As an open-source company, we welcome contributions through Github. Help us keep it up-to-date, accurate, and easy to understand by getting involved and sharing your ideas!