Developer Account Holder transfer checklist

Confirm authority and successor

Name the current Account Holder, successor, legal entity, business approver, finance owner, and release owner. Do not begin with a personal handoff if the organization has not agreed who should hold final account authority.

Review what the holder can affect: membership, agreements, team roles, certificates, identifiers, App Store Connect control, finance-adjacent workflows, and emergency escalation. The transfer is not only a login change.

AppReviewReady interpretation: Account Holder continuity protects revenue because a blocked holder can delay paid launches, account recovery, membership renewal, and urgent release fixes.

Choose a quiet transfer window

• Avoid transfer during App Review, major launch, account transfer, or payout investigation.
• Pause nonessential role, certificate, and agreement changes.
• Confirm the successor can sign in with two-factor authentication.
• Notify finance, release, and security owners before the change.
• Keep rollback or escalation contacts available during the window.

Map dependent operations

List workflows that may depend on holder authority: membership renewal, Paid Applications Agreement, bank/tax review, certificates, App IDs, team invitations, app transfers, and support escalations.

If the current holder also owns CI secrets, API keys, bank records, or vendor relationships, transfer those responsibilities separately. The Apple role change does not automatically move operational knowledge.

Separate Apple process from AppReviewReady interpretation: Apple provides the role-transfer workflow; AppReviewReady recommends a continuity ledger so the business can keep shipping and collecting revenue after the change.

Run a post-transfer rehearsal

1. Successor signs in and verifies trusted device access.
2. Review team roles, app access, agreements, membership, and certificates.
3. Confirm release owners can still submit, sign, and manage apps.
4. Confirm finance owners can still access required business records.
5. Record open issues and next audit date.

Account Holder transfer record

The record gives leadership a durable account-control trail. It also prevents future operators from guessing why authority changed during a launch period.

Review the record after leadership changes, acquisitions, or staff departures. Account control should not depend on personal memory or one founder's device.

After the transfer, schedule a permissions audit. Holder changes often expose stale users, outdated certificates, or finance access assumptions that were previously hidden.

Do not combine the holder transfer with unrelated account cleanup unless the situation demands it. First prove that the new holder can run the account; then remove stale users, rotate credentials, and change operational ownership in a controlled follow-up.

If a paid launch or B2B rollout is near, require explicit signoff from finance and release owners. The question is not only whether the transfer can happen, but whether the business can tolerate account-control churn during that window.

Holder transfer record:
Current holder: [name]
Successor: [name]
Business approver: [team]
Transfer window: [date]
Dependencies checked: [list]
Post-transfer rehearsal: [passed/failed]
Next audit: [date]