If your app runs on Siberian CMS today, you can move it to Your platform without starting over on Google Play: same store listing, same reviews, same ratings — your Your platform build publishes as an update to the same app. And your customers move with you.
What moves, honestly #
| Item | Moves? |
|---|---|
| Google Play listing, reviews & ratings | Yes — via your original signing keystore |
| App Store identity | Yes — via your original Bundle ID |
| Your customers (app users) | Yes — via the migration module |
| App design & content | Rebuilt — usually better, with Your platform AI (see guide 1) |
| Other module data (e.g. Appointment Pro bookings) | Not synced automatically — see the note below |
Be aware: data inside other modules — for example your appointment history in Appointment Pro — does not transfer automatically. Only customers transfer. If specific module data matters to you, contact our team and we’ll look at what’s possible for your case — reviewed individually, not guaranteed.
The plan: build first, then two sync steps #
First, build your app on Your platform the normal way (guides 1–3 — most people have a working version in an afternoon). Then migration itself is just two steps.
Sync your store details #
Android (Google Play)
Google recognizes your app by its package name and signing key. Both come from your Siberian backoffice:
- In your Siberian backoffice, open your app’s settings and find the Android section. You’ll see the store details — package name, key alias, store password and key password — and a Download the keystore file button. Download it and note all four values.
- In Your platform → Publication → Google Play, find the “Migrating from Siberian CMS?” box and drop your keystore there (accepted: .jks, .keystore, .pks, or a .zip containing the keystore).
- Enter the same package name, alias and passwords — exactly as they were in Siberian. Same values = Google Play accepts your new build as an update to your existing app.
The keystore is precious: if the key or passwords are wrong, Google Play will reject the update. Copy carefully, and keep a backup of the keystore file somewhere safe.
iOS (App Store)
Simpler: copy your Bundle ID from the Siberian backoffice and enter it in Your platform → Publication → Apple App Store. Same Bundle ID = same app on the App Store.
Sync your app users #
Recommended timing: do this step after your new app is live in the stores — sync the users last, and they arrive into a finished, working app.
Your customers — their accounts — move over with our free migration module:
- Download the migration module [DOWNLOAD LINK — MIGRATION MODULE] and install it in your Siberian backoffice like any Siberian module.
- A new Your platform menu appears in your Siberian backoffice. Open it → Customers Migration Export. You’ll see your customers with a readiness check (“6 customers — 6 ready to import, 0 would be rejected”).
- Press Export CSV (valid rows only) and download the file.
- On the Your platform side, import the file into your app — your customers arrive with their accounts.
Common questions #
- Will my customers notice?
- They keep the same app on their phone — it updates like any normal app update.
- My keystore is lost.
- Without the original key, Google Play can’t accept an update to the existing listing. Contact our team — we’ll help you check your options.
- Can you move my bookings / catalog / other module data?
- Not automatically. Ask us — we’ll assess your specific case, honestly and without promises.
