Legitimate app migration from personal to business account keeps getting rejected under Guideline 4.3(a)

Hello everyone,

I’m looking for advice from developers who successfully resolved a Guideline 4.3(a) “Spam” rejection in a legitimate account migration scenario.

Situation:

I originally developed and submitted my app under my personal Apple Developer account. Later, after creating a business/company, I opened a business Apple Developer account because I wanted the app published under the company instead. The original app on the personal account was removed before submitting on the business account. I changed the Bundle ID and created a new app entry under the business account.

However, the business-account submission was rejected under: “Guideline 4.3(a) - Design - Spam” with the message about “similar binary, metadata, and/or concept.”

I appealed and explained that this is the same legitimate app/business transitioning from an individual account to a company account, not a spam network or template cloning situation. The appeal was denied.

What makes this more confusing is that the app on the original personal account also later received a 4.3 rejection.

My questions:

Has anyone successfully resolved a similar “personal account → business account” migration issue? Did App Transfer end up being the only workable solution? If both accounts are already flagged with 4.3, what actually helped: major redesign, new features, metadata/screenshots changes, backend/content changes, or something else? Did anyone manage to get meaningful clarification from App Review? Is there any realistic path forward besides rebuilding/repositioning the app?

The app is a trading journal / analytics type app, so I understand it may also fall into a saturated category.

Any real experiences or advice would be greatly appreciated because the rejection messages are very generic and it’s difficult to understand what Apple specifically expects.

Thank you.

Legitimate app migration from personal to business account keeps getting rejected under Guideline 4.3(a)
 
 
Q