Your export can now move in: import a ZIP into any account

Import From Export ZIP is the CelestKin button that loads an archive made by Export My Data into a different account. To move your readings, export the ZIP from the old account, sign in to the new one, open Export My Data and tap Import From Export ZIP: birth profiles and readings merge in, and duplicates are skipped.

An export you can only look at is half a right. Portability means the data goes somewhere and works there. So the same ZIP that Export My Data produces can now be uploaded into another CelestKin account, and your birth profiles and readings simply continue there. New email, fresh start after a deletion, or a family member taking over the charts they care about: the archive is the bridge.

The round trip

In the old account: the gear icon at the top right, Privacy & Data, Export My Data, and save the ZIP somewhere you can reach it. Then sign in to the new account on the same screen and tap Import From Export ZIP. Pick the file, wait a few seconds, and the app tells you exactly what came across: "Imported 4 profiles and 31 readings." Run it twice by accident and the second pass imports nothing, because anything already present is skipped, not duplicated.

Moving to a new phone as well as a new account? Save the ZIP somewhere the new phone can reach, such as a cloud drive or an email to yourself, before you sign out of the old account. The import picker lists only .zip files, and the app checks the 20 MB size limit before it uploads anything.

Do credits and purchases move to the new account?

No. Credits, purchases and subscriptions never move; an import carries birth profiles and readings, and nothing else.

Transfers: your birth profiles (names, birth dates, times, places) and your readings, which are re-encrypted under the new account's key the moment they arrive. The plaintext from the ZIP is never stored.
Never transfers: credits, purchases, and subscriptions. Those are tied to the store account that paid for them, and an import that duplicated paid credits would be a counterfeiting machine. Chats also stay with the account they happened in.

Profiles are matched by name, ignoring capital letters. If the new account already has a profile called Mum, the Mum in the archive is skipped, even when the birth details differ, so rename one of them before importing if they are two different people. Each imported profile brings its name, birth date, birth time (or the flag that the time is unknown), birthplace and gender. Names are capped at 80 characters and places at 200.

Readings are matched on three things together: the profile name, the moment the reading was created, and its topic. A reading that matches all three is already there and is skipped. Everything else is added with its original date, so your history keeps its real timeline instead of bunching up on the day you imported.

A worked example shows how the matching behaves. The old account holds four profiles (Me, Mum, Dad and Sam) and 31 readings. The new account already has a profile called Me. The import adds Mum, Dad and Sam, skips Me because that name exists, adds all 31 readings, and reports "Imported 3 profiles and 31 readings." Run the same file again and the app answers "Everything in that archive is already in this account."

Re-encrypted is meant literally. The server reads each reading from the ZIP and seals it again with AES-256 in Galois/Counter Mode, specified in NIST SP 800-38D, under the importing account's own key, which it derives from that account's user id with HMAC-SHA256 as defined in RFC 2104. The ZIP on your phone, though, is plain readable JSON: treat it like any document that holds birth details, and delete it once the import is done.

Two guardrails: importing requires a full signed-in account, not a guest session, and the archive must be a genuine CelestKin export under 20 MB. Anything else is politely refused.

A few more limits sit behind those two. One import reads up to 5,000 profiles and 5,000 readings from the archive, and any single file inside that would expand past 100 MB is ignored, which stops a small ZIP from unpacking into something enormous. Import draws on the same three-per-24-hours allowance as export in that account. A guest who tries it sees "Sign in with a full account to import data." After a successful import, the app pulls the new rows down to the phone, so they appear in your history without a restart.

Why this matters more than it looks

The EU's data-protection working party, in its guidelines on the right to data portability (WP242), describes the right as receiving your data in a structured, commonly used and machine-readable format and being able to transmit it onward. Every app promises you can leave. Very few make the data useful after you do. A round-trippable export keeps us honest twice over: the export has to stay complete and readable or the import would break, and you can verify the whole loop yourself in two minutes with a test account. If anything in the loop ever fails you, that is a bug, and [email protected] wants to hear about it.

Carry your charts to the new account

Import From Export ZIP, on the Export My Data screen, adds your birth profiles and readings to a full account and skips any already present.

Coming soonApp StoreSoon