Move between Cloud and self-host

Your data is yours. You can leave Cloud for your own server, and the file you get is the same encrypted backup a self-hosted trckable writes and restores (Backups). A person on our side makes it: there is no export button yet.

Cloud to your own serverCopy Anchor Link

Email support@trckable.com from your account's address and say you want to move. We reply within 7 days with two things, sent separately: the backup file (.tkb) and its key.

1. We copy Cloud's data, remove every other customer's account from the copy, and write a new backup of what is left, locked with a one-off key. The file holds your sites, settings and analytics, and nothing of anyone else's. The key is not Cloud's own: it opens this file only.

2. On your server, with the key set, restore it into an empty directory:

   Copy Text

   export TRCKABLE_SECRET=<the key we sent>
   trckabled restore <file>.tkb /var/lib/trckable
   TRCKABLE_DATA_DIR=/var/lib/trckable trckabled serve

   Keep TRCKABLE_SECRET set the same way from then on, or copy its contents somewhere safe (why).

3. Set a password for yourself, because Cloud signs you in with a link and there is no password in the file:

   Copy Text

   trckabled admin reset-password you@example.com

4. Point your tracking snippet's address at the new server, and cancel the plan under Plan & billing (Cancel and delete).

What movesCopy Anchor Link

• Your sites, with their settings, reports and the analytics behind them: the reports on the new server show the same numbers as on Cloud (checked number for number, as in the restore test in Backups).
• The payments already recorded, and the people who had access to your account (each needs a password set with the command above).

What does notCopy Anchor Link

• Payment provider connections. The keys are locked with a key only Cloud holds, so they are not readable on your server, and payments stay off until you connect each provider again (how). Payments already recorded stay.
• Two-step sign-in. Authenticator codes cannot be checked on the new server. Set it up again after signing in; until then trckabled admin disable-2fa <email> turns it off for a person.
• Plan, invoices and billing. They live in Cloud and stay there.
• Single events. The analytics come as the aggregated store the backup holds; there is no raw export of single events (Leaving trckable).
• Events collected after the file was written. Move your snippet the same day, and ask us to write the file as late as you like.

Your own server to CloudCopy Anchor Link

Email support@trckable.com. This direction is not the same: Cloud keeps many accounts in one place, and it cannot yet open a self-hosted backup and add it to your account. Today you start in Cloud with fresh sites (sign up, add the sites, change the snippet), and your history stays on your server, where it keeps working and can still be restored from its own backups. Moving the history itself is on our list; ask us if it matters to you and we will say where it stands.