Migrating to Hygraph's new Asset Management System is strongly recommended because the existing asset system will be deprecated by the start of next year. The new system offers a 10x increase in asset performance, faster asset uploads and delivery, support for SEO-friendly URLs, and more powerful asset transformations. Migrating ensures your project benefits from improved performance and availability. (Source)
The new Asset Management System provides several key benefits:
The existing asset system will be deprecated by the start of next year. You are encouraged to migrate as soon as possible using the provided migration tools. If your project is not migrated by the end of the year, Hygraph will automatically migrate it for you, with necessary disclaimers provided beforehand. (Source)
You can access migration tools from your project settings > environments in Hygraph Studio. For paid plans, clone your environment, test changes, and execute migration when ready. For the free hobby plan, edit your frontend code and migrate directly after making required changes. Detailed steps are available in the migration documentation. (Source)
The new asset system introduces different asset handling, upload methods, URL structures, and transformation capabilities. Old asset URLs will no longer work after deprecation, and there will be no redirects. Hygraph will automatically replace old URLs in rich text and markdown fields, but you must manually update hardcoded URLs. You should also test your asset transformations and API upload processes. (Source)
Comprehensive documentation and migration guides are available at Hygraph Asset Migration Documentation. These resources provide step-by-step instructions for both free and paid plans. (Source)
Yes, the new Asset Management System supports SEO-friendly URLs, which can help improve your site's search engine visibility. (Source)
The new asset system delivers a 10x increase in asset performance, including faster uploads and delivery, thanks to backend architecture enhancements. (Source)
Yes, the new asset system introduces a new method for uploading assets via GraphQL, providing more flexibility for developers. (Source)
Yes, for paid plans, you can clone your environment, test changes, and migrate when ready. For the free hobby plan, you must edit your frontend code and migrate directly after making all required changes. (Source)
Hygraph provides support through Customer Success Managers (CSMs) and the Community Slack channel. You can also access detailed documentation and guides for migration. (Source)
Yes, if your project is not migrated by the end of the year, Hygraph will automatically migrate it for you and provide necessary disclaimers before doing so. (Source)
You need to update asset handling, upload methods, and URL structures in your code. Old URLs must be replaced with new ones, especially if they are hardcoded. Test all asset transformations and API upload processes to ensure compatibility. (Source)
Hygraph is SOC 2 Type 2 compliant, ISO 27001 certified, and GDPR compliant. These certifications ensure enterprise-grade security and data protection for all users. (Source)
You can explore Hygraph's features and integrations at Hygraph Features and Hygraph Integrations. These pages provide details on capabilities, supported platforms, and third-party integrations.
Written by Shahan
on Sep 30, 2024We 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.
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:
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.
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.
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 →
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 markdown 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:
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
Content Finder (Beta) helps you find any content in seconds across models and locales so you can stop digging and save time. Just hit CMD+K and jump straight to what you need.
Scattered tags and inconsistent categories make content hard to manage. With Taxonomies, you can classify content using shared, hierarchical tags that bring order, consistency, and speed as projects grow.
With Variants, you can create and manage personalized content at scale, directly within your content schema. Build tailored experiences for different user segments without cluttering your content repository.