How to transition users from individual to team plans while preserving their purchase history in Memberstack? Answered

Hey Memberstackers!

I'm seeking advice on a hybrid growth model: Layering Individual, Custom Group, and Team plans.
I'm mapping out a multi-stage growth strategy for my new service and would love to get insights from anyone who has built something similar. My goal is to support both bottom-up (individual) and top-down (team) acquisition without creating a confusing user experience.

Here’s the planned evolution:

1. Launch (Bottom-up): Start with Individual Plans only. Users sign up and pay for themselves. This will be my initial ad-driven acquisition channel.
2. Phase 2 (Viral Loop): Introduce a custom-built "Company Group" feature. This will be my own backend logic that identifies users from the same company (via email domain) and allows them to link their individual accounts to get shared benefits, without changing their individual billing.
3. Phase 3 (Top-down): Finally, add official Memberstack Team Plans to support managers who want to purchase and manage a block of seats for their team.

My core question is for anyone who has successfully layered these models. Specifically, I'm trying to anticipate any friction points:

• UX/UI: Did you run into challenges helping users understand the difference between being in a custom group (your own logic) versus a paid team (Memberstack's feature)?
• Custom Dashboards: Did you find it necessary to build a fully custom account dashboard to present these different relationships clearly, or were you able to make it work with the default Memberstack profile modal?
• General "Gotchas": Are there any other unforeseen issues or limitations I should be aware of when trying to make these distinct acquisition models coexist on the same site?

I'm trying to make smart decisions now to ensure I don't have to do a major rework later. Any "war stories" or advice would be incredibly valuable.

Oh and one quick follow-up question about the user experience when upgrading from an individual plan to a team plan.
I want to make sure a user's purchase history (the assets they've already bought) carries over seamlessly if they decide to upgrade from an Individual Account to a Team Account that they'll manage. My backend ties all purchased assets to the Memberstack userId.

My question is:

• What's the best practice for moving a user from a solo plan to a multi-seat team plan?
• If a user cancels their individual plan and subscribes to a new team plan, does their original userId persist? As long as it does, my backend can ensure they keep their assets. I just want to confirm this is the recommended flow, or if there's a more native "upgrade" path I should be using to make it smoother for the user.

Basically, I want to avoid any scenario where a user thinks they've "lost" their previous downloads when they upgrade to manage a team.

Thanks for any advice!