Moving to a New Server
Migrate PB Gig Diary to a new host or server without losing your data or licence.
Before you migrate
- Make a note of your licence key — it’s shown under Gig Diary → Settings → Licence
- Export your data as a backup — Gig Diary → Settings → Export (gigs, venues, artists, songs)
- If you use Google Calendar sync, note your Calendar ID — you’ll need to re-enter the credentials on the new server
Migration steps
-
Deactivate your licence on the old server
Go to Gig Diary → Settings → Licence → Deactivate this machine
-
Export your data
Go to Gig Diary → Settings → Export and download CSV exports of your gigs, venues, artists, and songs. Keep these safe.
-
Migrate your WordPress site to the new server
Use your host’s migration tool, a plugin like All-in-One WP Migration, or a manual database and files transfer. PB Gig Diary’s custom database tables will migrate with your WordPress database automatically.
-
Install PB Gig Diary on the new server
If the plugin didn’t transfer with the migration, download the latest version from purebaltic.co.uk and install it via Plugins → Add New → Upload Plugin.
-
Activate your licence on the new server
Go to Gig Diary → Settings → Licence, enter your licence key and click Activate.
-
Reconnect Google Calendar (if applicable)
Re-enter your service account credentials and Calendar ID under Gig Diary → Settings → Google Calendar and test the connection.
-
Verify your data
Check that your gigs, venues, songs, and setlists are all present. If anything is missing, use the CSV exports from step 2 to re-import.
If your data didn’t migrate
If your PB Gig Diary data didn’t transfer with the WordPress migration — for example if you’re doing a fresh WordPress install rather than a full migration — you can restore from your CSV exports:
- Import venues first — Gig Diary → Settings → Import
- Import artists (Agency licences)
- Import songs
- Import gigs — venues will be matched by name
Changing domain
If your domain name is changing as part of the move, the licence deactivation and reactivation process is the same. Licences are tied to machine activations, not domain names, so a domain change on its own doesn’t require any licence action.

