Skip to main content

Migrating Your Existing App to Tapcart

Updated this week

Migrating Your Existing App to Tapcart

If you already have a mobile app published in the App Store or Google Play Store, Tapcart can update over it, your customers won't need to download a new app. This guide covers what to expect during the migration process, how it works behind the scenes, and what to communicate to your customers.

In this article:

  • How Tapcart migrates over your existing app

  • iOS migration steps

  • Android migration steps (including upload key reset)

  • What your customers will experience

  • Communicating the update to your audience

How It Works

Tapcart publishes app updates using your existing app's Bundle ID (iOS) and Package Name (Android). Because we use the same identifiers, the App Store and Google Play treat it as an update to your current app, not a new listing. This means:

  • Your existing app store listing, ratings, and reviews are preserved

  • Customers with auto-update enabled will receive the new version automatically (typically overnight on Wi-Fi)

  • Customers without auto-update can manually update from the App Store or Google Play

  • The app URL and download link remain the same

iOS Migration

For iOS, the migration is straightforward once Tapcart has been invited to your Apple Developer account with Admin access:

  1. Tapcart builds your new app using your existing Bundle ID

  2. The build is submitted as an update to your current App Store listing

  3. Apple reviews and approves the update (typically 24–48 hours)

  4. The update is released to your customers

Prerequisite: Ensure your PLA (Program License Agreement) is accepted in App Store Connect. An unsigned PLA will block the submission.

Android Migration

Android migrations may require an additional step to reset your app upload key. This is necessary when the previous app provider used a different signing key.

  1. Your Implementation Specialist will check whether an upload key reset is needed

  2. If required, you'll need to submit a key reset request through Google Play Console:

    • Go to Google Play Console → Setup → App signing

    • Follow the prompts to request an upload key reset

    • Google typically processes this within 2–3 business days

  3. Once the key is reset, Tapcart can submit the updated build

  4. Google reviews and approves the update

Your Implementation Specialist will guide you through this process. If you're unsure whether an upload key reset applies to you, just ask,we handle this regularly.

What Your Customers Will Experience

Scenario

What happens

Auto-update enabled

The app updates automatically, usually overnight on Wi-Fi. The customer opens the app and sees the new Tapcart experience.

Auto-update disabled

The customer will see an "Update" button in the App Store or Google Play. They need to tap it manually.

New customers

Anyone who downloads the app after the update goes live will get the Tapcart version immediately.

What is preserved: App store listing, ratings, reviews, and download link.

What changes: The in-app experience transitions to the Tapcart platform. Push notification subscribers are retained as long as the app certificates remain the same (your IS will confirm this).

Communicating the Update

We recommend proactively informing your customers about the app update. This helps users without auto-update enabled get on the latest version quickly.

Suggested channels:

  • Push notification: Send a push to existing app users announcing the update

  • Email campaign: Include a note in your next newsletter or send a dedicated announcement

  • Social media: Post about the refreshed app experience

  • SMS: If you use SMS marketing, a quick message drives fast adoption

Sample message: "We've updated our app with a fresh new look and faster shopping experience! Open the App Store or Google Play and update to the latest version."

Migration Checklist

  • ☐ Tapcart has Admin access to your Apple Developer account

  • ☐ Tapcart has been invited to your Google Play Console

  • ☐ PLA is accepted in App Store Connect

  • ☐ Upload key reset completed (if applicable for Android)

  • ☐ App listing assets updated (icon, screenshots, description)

  • ☐ Test build reviewed via TestFlight (iOS) and/or internal test track (Android)

  • ☐ Customer communication plan ready for launch day

More Questions

Have more questions? We're happy to help! Please reach out to us through LiveChat on your dashboard or email us at [email protected].

Did this answer your question?