Frequently Asked Questions

Asset Management System Migration

What is the new Asset Management System in Hygraph and why should I migrate?

The new Asset Management System in Hygraph, released for all new projects since March 2024 and now available for existing projects, is designed to improve performance and reliability. It delivers a 10x increase in asset performance, faster uploads and delivery, a new GraphQL upload method, SEO-friendly URLs, and more powerful transformations. Migration is strongly recommended because the old asset system will be deprecated by the end of this year. Note: The new system uses different asset URLs, and old URLs will stop working after deprecation. Read the official migration documentation for details. Best fit for teams seeking improved performance; teams unable to update hardcoded URLs may face challenges.

When will the old asset system be deprecated, and what happens if I don't migrate in time?

The old asset system will be deprecated by the end of this year. If you do not migrate your project by then, Hygraph will automatically migrate your assets for you, with necessary disclaimers provided beforehand. After deprecation, old asset URLs will no longer work, and there will be no automatic redirects. Note: Projects with hardcoded asset URLs must update them to avoid broken links. Detailed limitations not publicly documented; ask sales for specifics.

How do I migrate my project to the new Asset Management System?

You can access migration tools from your project settings > environments in Hygraph Studio. For paid plans, clone your environment to a migration environment, update your frontend code, test for breaking changes, and then execute the migration. For Community (free/hobby) plans, you must manually edit your frontend code and migrate your master environment directly. The migration tools are only available in Hygraph Studio. For full steps, see the migration guide. Note: Migration for free plans requires more manual effort and code changes.

What changes are required in my code and asset URLs during migration?

The new asset system uses a different URL structure for serving assets, and there are no redirects from old URLs. Hygraph will automatically replace old URLs in rich text and markdown fields, but you must manually update hardcoded asset URLs in your code. You should also test your application for any breaking changes related to asset handling, upload methods, and transformations. Note: Failure to update hardcoded URLs will result in broken assets after migration. Best fit for teams able to update code; teams with legacy codebases may need extra effort.

What are the main benefits of the new Asset Management System?

The new system delivers a 10x increase in asset performance, faster uploads and delivery, a new GraphQL upload method, SEO-friendly URLs, and more powerful asset transformations. These improvements enhance both performance and availability for content delivery. Note: Migration is required to access these benefits; teams unable to migrate may not see performance gains.

Where can I find detailed migration documentation and support?

Comprehensive migration documentation is available at Hygraph Asset Migration Guide. For additional support, you can reach out to your Customer Success Manager (CSM) or join the Hygraph Community Slack channel. Note: Some migration scenarios may require direct support; contact Hygraph if you encounter blockers.

Features & Capabilities

What new features does the Hygraph Asset Management System provide?

The new system introduces faster asset uploads and delivery, a new GraphQL-based upload method, SEO-friendly asset URLs, and enhanced transformation capabilities. It also provides a new URL structure for serving assets. Note: Some transformation features may differ from the old system; test your use cases before migrating. Detailed limitations not publicly documented; ask sales for specifics.

Does the new asset system support SEO-friendly URLs?

Yes, the new asset system supports SEO-friendly URLs for assets, improving discoverability and search engine optimization. Note: Old URLs will not redirect; ensure all references are updated. Best fit for teams prioritizing SEO; teams unable to update URLs may not benefit.

Can I upload assets using GraphQL in the new system?

Yes, the new asset system introduces a method to upload assets using GraphQL, enabling more flexible and modern integration with your tech stack. Note: You may need to update your integration code to use the new upload method. Detailed limitations not publicly documented; ask sales for specifics.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant, ISO 27001 certified, and GDPR compliant. These certifications ensure that your content and assets are managed in a secure and compliant environment. For more details, see the Secure Features page. Note: Asset-specific compliance limitations are not separately documented; contact Hygraph for asset-specific compliance questions.

How does Hygraph ensure the security of my assets during and after migration?

Hygraph provides enterprise-grade security features, including encryption at rest and in transit, granular permissions, audit logs, and automatic backups (for enterprise plans). The migration process is designed to maintain data integrity. For additional assurance, penetration testing is available as an add-on for enterprise customers. Note: Some advanced security features may require an enterprise plan; ask sales for specifics.

Technical Requirements & Documentation

Where can I find technical documentation for the new asset system and migration process?

Technical documentation for the new asset system and migration process is available at Hygraph Asset Migration Guide. Additional resources include API references, content modeling guides, and integration documentation at Hygraph Documentation. Note: Some advanced migration scenarios may require direct support from Hygraph.

Customer Feedback & Success Stories

What feedback have customers shared about using Hygraph and its migration process?

Customers have praised Hygraph for its intuitive interface and ease of use. For example, Anastasija S. noted, "Every change I make to Hygraph I can instantly see on the front-end," and Charissa K. described it as having a "great UI, fast to comprehend and localizable CMS." Hygraph has been voted #1 in Enterprise Usability for three consecutive years. Note: Specific feedback on the asset migration process is not separately documented; ask sales for migration-specific testimonials.

Which industries and customers have successfully used Hygraph?

Hygraph is used by organizations in SaaS, eCommerce, media, consumer goods, technology, education, healthcare, automotive, and more. Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, HolidayCheck, and Statistics Finland. For example, Komax achieved a 3X faster time-to-market by managing 20,000+ product variations and 40+ markets via one CMS. See more at Hygraph's case studies page. Note: Asset migration results for these customers are not separately documented.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Watch now

Our new Asset Management System is now available for existing projects

Enhance performance and availability by switching to our new Asset Management System. We strongly recommend migrating as soon as possible using our migration tools, as the existing asset system will be deprecated by the start of next year.
Shahan Syed

Last updated by Shahan 

Jan 21, 2026

Originally written by Shahan

Mobile image

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.

Read the documentation →

#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. Asset System Migration.png

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.

Asset System Migration for Free Plans.png

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 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:

Asset System Migration Scenarios.png

Read the complete guide →

#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

Shahan Syed

Shahan Syed

Shahan is the Product Marketing Manager at Hygraph. Living in Pakistan, he loves to spend time exploring places, pencil sketching, reading, and watching science fiction and K-dramas.

Share with others

Sign up for our newsletter!

Be the first to know about releases and industry news and insights.