Context

When migrating from a personal account to a team account in Codemagic, you may wonder whether your existing code signing certificates, provisioning profiles, and related credentials carry over automatically. This article explains what happens to your signing identities during migration and how to set them up in your new team account.

Answer

Code signing credentials do not transfer automatically when moving from a personal account to a team account. Personal and team accounts are treated as separate entities in Codemagic, so all signing identities and environment variables must be re-configured under the team account.

Follow the steps below depending on your signing approach:

Manual Code Signing

1. Go to Team Settings → codemagic.yaml settings → Code signing identities.

2. Re-upload your iOS certificates and provisioning profiles.

3. Re-upload your Android keystore file.

Note on Android Keystore: When uploading an Android keystore, you will be prompted for two passwords — the keystore password and the key password. Depending on how your keystore was created, these may be the same value. If you only set one password when generating your keystore, enter that same password in both fields.

Automatic Code Signing (iOS)

1. Go to Team Settings → Integrations → Developer Portal.

2. Re-connect the Apple Developer Portal integration.

3. Add your App Store Connect API key under Manage keys.

This integration is configured separately per team, so your personal account's API key will not carry over.

Environment Variables

Environment variables are scoped to the account or team and do not transfer. This includes any secure variables holding signing credentials such as keystores or private keys. Re-add all required environment variables under your team settings before running your first build.