Having popular IPs means nothing if:
A: You don't have enough people to work on them in general, especially if some of them do leave. Nintendo already has most of their developers on other projects. They aren't suddenly just going to be moved to different projects just because they suddenly have access to new IPs that don't have people developing for them.
B: You don't have developers who know how to work and develop for those IPs or want to develop for those IPs. A Big Square IP on Nintendo means nothing if there's no one who wants to develop it or if Nintendo themselves aren't confident in another team wanting to develop for it. Sacrificing most, if not almost, all of the talent for an IP would more than likely prevent the IP from starting back up, something which fans and gamers want to certainly avoid.
And Employees are still people and whether they want to work for a company or not is still their decision. To some, what they want to develop and what-for is more important than money. If they don't want to develop for Nintendo only, that's their decision.
I think you're catastrophizing acquisitions. How many acquisitions have been made where companies lose the majority of the workforce they just obtained? I don't think that happened once with Microsoft, not even with Rare, and they've been eating companies like tic-tacs.
The dichotomy of "buying for manpower" or "buying for IP and thus losing the employees" doesn't even make sense as the two options, those aren't even opposites of each other. When a company is bought for the workforce, what makes that purchase different in terms of employee retention than the other? They could just leave as well. The difference of owning an IP doesn't change that.
The factor you're hinging dissolution/retention on isn't even directly related to this... whether they own an IP?
"We bought
x and it all went smoothly. But then we tried to buy
y and everyone left!"
"Well, do they own IP?"
"Yeah, a few"
"Well, there's your problem"
"I don't want to work for Nintendo, but our dev never owned IP, so I guess I won't quit."
Like, it doesn't even make sense. They're not connected.
You seem to be treating this as if they were buying Konami or something, where they get a bunch of IP, but they barely absorb anyone to actually work on them. Buying a competent company like Capcom or Square or Bamco would come with all the designated teams as well. You wouldn't need to form teams for them. You could reorganize them... but if their system already works, no real need to fix it. Look at how Sega barely touched Atlus.
When MS bought Bethesda, they didn't have to create teams for Doom or Fallout or ES, those already exist. And losing so many employees those teams fall apart is completely unfounded, it clearly didn't happen. What, are all the Square employees going to revolt because Sony now owns their company?
This is clearly fearmongering. Yeah, there probably will be turnaround after an acquisition, but people leaving in droves because they don't want to work for Nintendo? Did that happen with Sony? Microsoft? Embracer? Tencent? ****ing
Disney? Not really. Not to the extent the acquired dev collapsed and necessitated the parent company to completely rebuild it.
But it's going to happen to... Nintendo? The Japanese market leader and presumable pretty good employer? Are they all team Sonic?
Or maybe they find it difficult to develop for a Nintendo system or find it easier to develop for a different console or system. And it's easy to understand why somebody would develop for something they have experience with than having to start getting used to a different system they have no experience developing for. Nintendo may be pretty open to letting some of their companies do what they want to do like Monolith, but that doesn't mean some employees would just suddenly be okay developing for them if their company gets bought by them, whether it'd be they have more experience with developing for other systems or they don't want to develop solely for Nintendo only.
Ok, so... the devs find it
so difficult to decipher Switch architecture (despite Nintendo granting them proprietary dev tools now that they're subsidiaries) that, instead of familiarizing themselves (as is their job), enough give up that it
depletes the whole studio? Seriously? This isn't porting GTA6 to Switch, this would be an experienced dev creating native Switch software with Nintendo's help and tools. Even tiny, relatively inexperienced indies can navigate the system.
But so many people can't figure out that even the art department leaves.
"I heard Capcom fell apart"
"Oh, how'd that happen"
"They tried to make a Switch game"
You think if a current division of, like, Square, gets tasked making a Switch game now... they would just
quit? You think if a programmer quits then applies at another company and says they refuse to learn the architecture of the currently most popular system... that will be a desirable hire? Do devs quit when a new system comes out but they have more experience with the old one? Part of the job for every developer is learning new hardware.
And apparently the way to avert all of this is just to not own any IP. Devs who don't own IP are non-partisan. Devs who own IP very well may leave en masse because they don't want to learn the system they're paid to develop for. This is, like... nonsensical alarmism.