Whether you can move individual resources between subscriptions of different tenants depends on the type of resource. Azure has specific guidelines for what can and cannot be moved.
You can check here :
If direct transfer is not possible, you might need to export the data from services like Cosmos DB, SQL, and Storage Accounts, and then import it into the new tenant.
Organizations might have several Azure subscriptions. Each subscription is associated with a particular Microsoft Entra directory. To make management easier, you might want to transfer a subscription to a different Microsoft Entra directory. When you transfer a subscription to a different Microsoft Entra directory, some resources are not transferred to the target directory. For example, all role assignments and custom roles in Azure role-based access control (Azure RBAC) are permanently deleted from the source directory and are not transferred to the target directory.
When you move a subscription, it should include all the resources within that subscription, including VNETs and their configurations like subnets, peering, NSGs... However, you need to check for any dependencies or configurations that might require manual intervention.
Keep in mind that moving a subscription does not inherently move the data stored in services like Cosmos DB, SQL databases, and Storage accounts. The data associated with these services is part of the subscription, so if the entire service (for example the SQL server, Cosmos DB account) is moved, the data should also move with it.
When moving a subscription to a new tenant, you generally don't need to create a new subscription in the target tenant. The existing subscription is transferred to the new tenant, retaining its name and ID. However, post-migration, some settings might need to be reconfigured, like Azure policies and access controls.