Note: This applies to individual Greyscalegorilla subscribers migrating from the Hub or Studio.
In short, no. Cargo represents a significant update to how Greyscalegorilla delivers assets. The Hub and Studio used a variety of image and model formats depending on the asset type. Cargo standardizes this into a streamlined pipeline: textures are delivered as JPEG or PNG, with the option to choose between them, and 3D models are converted automatically to your DCC's native format behind the scenes. You never interact with the underlying files directly.
Because the underlying file formats and delivery structure are fundamentally different, assets downloaded through the Hub or Studio aren't recognized by Cargo's asset management system. The two platforms speak different languages, so to speak.
What this means for you
Assets downloaded from the Hub or Studio will continue to work in your projects as they always have. Cargo simply won't be able to see, track, or update them as part of your library.
If you want the Cargo version of an asset, you'll need to download it fresh through Cargo. The Cargo version will use the new pipeline: if it’s a material, JPEG, or PNG textures based on your preference, and models delivered ready to use in your application of choice.
How to transition
The cleanest way to move to Cargo without disrupting existing work:
Keep using Studio for active projects. Continue working the way you have been until those projects are complete. Don't delete your Studio assets — you'll want them available if you ever need to reopen an archived project and have everything work as expected.
Introduce Cargo on new projects. When starting something new, use Cargo from the beginning. Cargo downloads assets into its own Cargo Kits folder by default, so your Studio and Cargo libraries will naturally stay separate without any additional configuration.
Note: This only matters if you were downloading Studio assets to a single shared folder, which is how Studio works by default. If you were collecting assets into a TEX folder next to each scene file, your projects are already self-contained and there's nothing to worry about.
This way you're never disrupting work in progress, and your Cargo library builds naturally over time as you take on new projects.