A step-by-step migration guide to help you export your collection and metadata from HeyMint Launchpad to your preferred IPFS host before the platform shuts down.
Last updated
Was this helpful?
After a lot of thought, the HeyMint team has made the tough decision to sunset the HeyMint platform, including Launchpad, Quests, and all related services as it’s no longer sustainable for us to continue operating in the current market environment. We’ll be officially signing off all services on May 31, 2025.
This means that hosting for collections and metadata pinned via our IPFS will also come to an end and eventually become unavailable. To help make this transition as smooth as possible, we’ve put together a migration guide to support you and avoid any disruptions to the collections you’ve trusted us with.
May 31, 2025 – Art and collection generation services will close, and new user sign-ups will be disabled.
For ERC-721A – You can follow the full steps outlined below on this page.
Thank you for trusting us with your NFT collection and for being part of our journey in Web3. While it’s tough to say goodbye, we want to make sure you can continue managing and staying connected with your project even after HeyMint shuts down.
To start migrating your collection, please head over to launchpad.heymint.xyz and follow the steps to export your assets and move them to a new IPFS host.
Please note: depending on the size of your files and metadata, there may be additional costs when uploading to a different IPFS provider.
From your Launchpad dashboard, select the project or collection you'd like to begin migrating.
Keep in mind: migration only applies to projects that have been deployed to the blockchain (mainnet or testnet) and are currently using HeyMint’s IPFS hosting for their images and metadata.
If your project is already using your own IPFS host, there’s no need to take action - your assets won’t be affected by the shutdown.
In your Launchpad dashboard, head to the left-hand sidebar and click on Export Collection. This option will only be visible if your project has been deployed to the blockchain.
When starting the export, please keep the browser tab open to avoid any interruptions while your files are downloading and updating.
Start by selecting the first action: Download collection images. Follow the on-screen prompt and choose a folder on your computer where the images will be saved. Once the download is complete, double-check your local folder to make sure everything came through.
Just a quick note: depending on the size of your collection, your chosen IPFS provider may charge for additional storage (see below for more info).
After uploading your images to your chosen IPFS host, copy the CID (Content Identifier) and paste it into the “CID for image files” input box in your Launchpad dashboard. It should look something like this: bafyxxxxxxx (with the "x" being random characters). Once entered, click Save image CID.
Next, go to “Process and download the updated metadata with new image URI” and click “Update Metadata.”
This step may take a little time - it will gather your collection’s existing metadata and replace the old image links with the new CID you just saved. Once the process is complete, download the updated metadata as a ZIP file.
After downloading, please check that the ZIP file is not empty and contains all the updated metadata files (they’ll appear as numbered files without a file extension).
If you'd like to double-check that the image and animation URLs in the metadata have been updated correctly, you can drag any of the metadata files into your browser to view its contents. See the example below for a comparison.
In the original metadata, you’ll see a different CID in the image field:
bafybeibxq6bezazq2iwdhk5p23fwsllbz6372kvulabouxmsuwv35k2gbm
In the updated metadata generated by the migration tool, you'll see that it now uses the CID you saved earlier:
bafybeihwusrv4unp3mxdncfhg6rikbtasjprcy4kndhniwnldjofnkhyba
Once you’ve confirmed the updated metadata files are complete, head over to your chosen IPFS provider and upload all the files together in one folder. This will generate a new CID for your metadata, which you'll copy and use in the final step.
We've included a video walkthrough below that covers this step (along with Step 6), shown using a Windows setup. The process is the same for both 721A and 1155 projects, so you can follow along regardless of your collection type.
Now that you have your new metadata CID, head back to your dashboard and input the updated IPFS URI. The format should be:
For this example, it would be:
Click Validate & Save, and once everything checks out, you’ll be prompted to sign a transaction through MetaMask. This will update your collection’s metadata on the blockchain.
You can refer to the video below to see how the update process works and how to confirm that the metadata has been successfully changed.
Here are the details of the test collection used in the recording:
You can also confirm if the update was successful by checking your project through a blockchain explorer.
Here’s how to check:
In the sidebar, click Smart Contract
Under the Overview tab, click the Contract Address. Make sure your contract is marked as Verified
If it’s not, you’ll need to click Verify Now and complete the verification before continuing
In the blockchain explorer, click on the Contract tab, then select Read as Proxy.
Note: This option will only appear if your contract has been verified. If you don’t see it, please go back and complete the verification step first.
Scroll through the available methods and look for either:
tokenURI – for 721A projects
uri – for 1155 projects
Click on the appropriate method, enter the token ID you want to check (e.g. 1), and click Query. The current metadata URI for that token will appear below.
You can also check out the video below, which walks through the steps above using a 721A project. The process is nearly the same for 1155 projects—the only difference is that you'll use the uri method instead of tokenURI.
Once you've completed all the steps and confirmed that your metadata URI now points to your own IPFS host, your migration is officially complete. You've successfully exported your project's metadata and assets to a location you fully control.
After you changed the token URI, make sure to go to one of the marketplaces, refresh metadata of one of the NFTs, and make sure it still displays correctly.
Once you've completed all 9 steps, your collection will be updated and ready to go with its new image and metadata CIDs. Your smart contract remains on-chain and fully functional - HeyMint was just the launchpad, and your project lives on.
Thank you again for being part of HeyMint 💜
– Due to the structure of ERC-1155 collections, please continue to the ERC-1155 Migration Guide for specific instructions.
After confirming that your images have been successfully downloaded, go ahead and upload them to the IPFS host of your choice - such as , , or .
(also known as Storacha Cloud)
You can use gateways like or to view your uploaded assets using the CID, as shown in the examples below.
In this , you'll see how to:
Go to Pinata and create an account:
In this example, the CID provided after uploading the updated metadata is:
You can view the contents of this CID here:
OpenSea (Testnet) collection link:
Project contract on Sepolia:
In our example, the project is deployed on Sepolia (Ethereum), so we'll use as the explorer.
If you run into any issues or have questions along the way, feel free to reach out to us at . We'll continue to support users until our closure, but please note that response times may be a bit slower than usual as we operate at limited capacity.
tokenURI method, the expected result should follow this format:
ipfs://<cid>/<token ID>
For example:
ipfs://bafybeihzx37ul3oucta45yb2paxqesloa66lccs6liamydsi45hw5feqlm/1
You can view a sample contract here: