As a protocol developer

If your protocol mints, transfers, escrows, delegates (freezes), revokes or burns NFTs you would have to add support for MIP. If you don’t do that your protocol will not work with migrated collections. You program will not be able to perform aforementioned operations.
You need to be on the “allow list” and not be in the “deny list”. It’s up to creators to choose those, but there will be defaults provided by Metaplex and hopefully ones governed by the community. (See below FAQ on how to get on the default list and etc)
- There are specific requirements that need to be met for your program to be added to the allow/deny list maintained by Metaplex. You can find them here.
- Expand to see requirements
The migration starts on January 27, 2023 as per this recent announcement:

What it means is that it’s technically possible that the first set of collections will initiate upgrades on that date. It will be up to their creators to decide when to start the actual migration. It doesn’t mean that all collections that opted-in will upgrade all at once. Likely it will be a cascading upgrade over the course of the next 90 days. After the 90-day window, it will not be possible to migrate existing collections.
The new standard is backwards compatible and after program upgrades it should “work” with “normal" NFTs just as well as pNFTs.
If your protocol has NFTs locked in escrow accounts, or NFTs frozen in users’ wallets you don’t need to worry. After migration those would also be migrated and will remain in escrow or frozen in user’s wallet. If your program was upgraded to support MIP it will continue to work as before with no disruption to users or any other things that need to be done on your or user’s side. (assuming your program is on allow/deny list for that collection)
Make sure you read “What do you need to know As a creator / collection owner” to get more context and understand the process from a creator’s point of view.
If your protocol uses escrow-accounts there is an extra step that you would have to make.

For technical details please read the official documentation:

For an official FAQ refer to:

If you need advice or technical support please join our telegram group: