We released our new Asset Management System earlier this year for improved performance and reliability. This was available for all new projects created since March 2024.
The new asset system is available for existing projects as well, and you can now migrate using our tools.
We are gradually rolling out our migration tools, and you will receive an email notification once they become available. You can access the migration tools from your project settings > environments.
The process for paid projects involves cloning your existing environment to a migration environment and testing for any breaking changes. Once everything seems fine, you can execute the migration, and we will handle the rest.
For the hobby plan, you will have to make changes to your code and directly migrate once complete.
Note: We will be deprecating our existing asset system by the start of next year and recommend you switch as soon as possible.
#Recap: our new redesigned asset system
Our new Asset Management System has been developed with a clear focus on improving performance and availability. The changes we’ve implemented in the backend architecture have resulted in a 10x increase in asset performance.
The new system offers:
- Faster asset uploads and delivery.
- A new method to upload assets using GraphQL.
- A new URL for serving assets.
- Support for SEO-friendly URLs.
- More powerful transformations.
#Overview of the migration process
We have a new workflow within the app and detailed documentation available to ease your migration process. You can access the migration tools from your project settings > environments.
The migration process differs depending on whether you are on a free or paid plan.
Paid Plans
If you are on a paid plan, you can clone your existing environments to a migration environment, make relevant changes to your frontend code, and test the changes in this new environment.
Once you have ensured everything works fine, you can migrate your master environment (or other environments) by selecting start migration.
Community Plan
If you are on a free hobby plan, you’ll have to edit your frontend code and directly migrate your master environment to the new asset system once you have made all the required changes.
Read our documentation for the complete migration steps →
#Required changes
The new asset system has a different approach to asset handling, upload methods, URL structures, and transformation capabilities.
The new asset system serves from a different URL; there will be no redirects, and the old URLs will no longer work after we deprecate the old asset system.
To ease the process, we will automatically replace the old URLs contained within rich text and string fields. This means that we will automatically handle assets embedded in your content.
However, you need to replace the old URLs with the new ones in places where they are hardcoded and test them out.
We also have a new process for uploading assets via the API, and the exact transformations supported in the new system differ.
Here are a few examples of scenarios where you would need to test and make changes:
#Timelines and deprecation of the existing asset system
We plan to deprecate our existing asset system by the end of this year and offer the next few months as a time to carry out the migration yourselves.
For projects that are not migrated by the end of the year, we will automatically migrate them for you, providing the necessary disclaimers before doing so.
As always, feel free to reach out to us for any questions through your CSMs or our Community Slack channel.
Blog Author