Switching from another app builder

Mobile App BuilderWritten by SeriUpdated 6 min read

Already have a Shopify mobile app from another builder? Here's what to ask your current provider for, how app transfers work at Apple and Google, and how your customers get the eBazoo version as a normal update.

In this article
  1. Step 1: Find out where your app is published
  2. Step 2: What to ask your current provider for
  3. Step 3: If your app needs transferring
  4. Step 4: The Android upload key or Play App Signing
  5. What carries over and what doesn’t
  6. How the update reaches your customers
  7. Try it before you decide
  8. Questions?

If your store already has a mobile app made with another app builder, you don’t have to start over in the stores. When the eBazoo version is published to the same App Store and Google Play apps, it reaches your customers as a normal update, and your listings, reviews and installs stay where they are.

This guide is the checklist for getting there. Most of it is about where your app lives today and what your current provider needs to hand over.

Step 1: Find out where your app is published

This is the most important thing to check first. Ask your current provider, or look for yourself:

  • In your own developer accounts. You can sign in to App Store Connect and Google Play Console and see the app there, and you’re the Account Holder (Apple) or owner (Google). You’re ready for the next steps.
  • In your provider’s accounts. The app shows your store’s name, but it sits in an account that belongs to them. They need to transfer it to your accounts first (Step 3).

eBazoo publishes apps only in the merchant’s own accounts. See Publish your app to the App Store and Google Play.

Step 2: What to ask your current provider for

Before you cancel anything, ask them for:

  • The app’s identifiers: the iOS bundle ID and the Android package name. They often differ from each other. The eBazoo version has to use the same ones, or the stores treat it as a new app.
  • The current version numbers on both stores. Each update must have a higher version number than the one that’s live, or the store rejects it.
  • The Android upload key (the keystore file and its passwords), or confirmation that the app uses Play App Signing (more in Step 4).
  • An app transfer to your accounts, if the app is in theirs (Step 3).
  • A list of what your app uses: features, sign-in options (for example Sign in with Apple) and connected services such as Firebase or analytics.

Tip: Ask for keys and passwords through a secure share, not in a plain email, and keep them somewhere safe. Don’t send them to anyone by email, including us.

Step 3: If your app needs transferring

Both Apple and Google let an app move from one developer account to another. The listing, reviews and installs move with it.

App Store

  • Your provider’s Account Holder starts the transfer, and your Account Holder accepts it.
  • The app needs at least one version released on the App Store, and it can’t be waiting for review, in review or pending release.
  • Both accounts must have accepted Apple’s latest agreements.
  • TestFlight builds and testers are removed first.
  • If the app uses Sign in with Apple, extra steps keep your customers’ sign-ins working.

Google Play

  • Your provider starts the transfer in Play Console, and you approve it.
  • Both developer accounts must be registered and active. Google asks for each account’s registration transaction ID.
  • Links to Firebase, Google Analytics and Google Cloud don’t move with the app and need setting up again.
  • Signing keys don’t move automatically. After the transfer, check the upload key (Step 4).

If you don’t have developer accounts yet, create them first. Publish your app to the App Store and Google Play explains how.

Step 4: The Android upload key or Play App Signing

Google Play only accepts an update signed with the app’s upload key. There are two ways to have it:

  • Your provider hands the upload key over, with its passwords. Whoever builds your updates can then keep signing the same app.
  • The app uses Play App Signing, and the owner of your Play Console account asks Google for an upload key reset to a new key. This works even if the old upload key is lost or your provider doesn’t send it.

Play App Signing is on for most apps created in recent years. In Play Console, open the app, then Test and release → App integrity → App signing to check.

On iOS, nothing like this needs handing over. Certificates and profiles live in your own Apple account, and a new one can be created there.

What carries over and what doesn’t

Carries over, as long as the eBazoo version goes out as an update to the same apps:

  • Your App Store and Google Play listings
  • Your ratings and reviews
  • Your installs: customers who have the app keep it and get the update

Doesn’t carry over by itself:

  • The app’s design and features. Your eBazoo app is built in Mobile App Builder. The AI App Generator builds a first version from your own catalog, and you can shape it in Design Studio. Features your old app had that eBazoo doesn’t offer won’t be in the new version.
  • Connected services like Firebase or Google Analytics after a Google Play transfer. They need setting up again.

Tip: Make a list of what your customers use most in your current app, and check it against Mobile App Builder before you switch. If you’re not sure about a feature, ask us (below).

How the update reaches your customers

The eBazoo version is published with your app’s existing bundle ID and package name, from your own developer accounts. Apple and Google review it like any other update. Once they approve it, your customers get it through the App Store and Google Play the same way they get any update, and new customers download the new version from your existing listing.

Apple and Google decide on approval, so nobody can promise a date for the switch.

Try it before you decide

You can try Mobile App Builder free for 14 days on Basic, Growth or Scale, and see your app in eBazoo Live before anything goes to the stores. Publishing needs a plan from Basic up. See Plans and billing.

Questions?

In Mobile App Builder, open Help & Support, click Contact support and choose the topic Publishing & app stores. Tell us how your current app is published and what it uses most, and we’ll tell you honestly what we cover today.

And if you ever want to leave eBazoo, you won’t be locked in: see Leave any time: your exit kit.

Still need help?

Talk to the team.

The people who build the apps answer every request.

Help & Support in the app

The quickest way. Your store details come with your request, and our reply arrives in the app and by email.

Email hello@ebazoo.com

For anything else, or if you can’t open the app.

Have us set it up

Publishing, setup and custom work, done with you by the eBazoo team.