Prepare a recoverable Plan database migration
Changing Plan's database destination can produce an apparently empty dashboard if historical records were not migrated. Treat the change as a data migration rather than a hostname edit. Keep collection consistent while following the database-management procedure for the installed release.
Record the starting point
Record the current storage type, destination and Plan version on every component that writes to it. Identify a few old sessions and one recent session for later comparison. Make a restricted database checkpoint and save configuration without publishing credentials.
Work through the change
- Read the current Plan database-management instructions and select the documented path for your source and destination. Confirm the destination is accessible using the intended service account.
- Plan a maintenance window for writers so data does not continue changing unnoticed during transfer. Follow the documented migration controls instead of copying live database files blindly.
- Update only the required storage configuration and complete the supported migration. Keep the original database available privately until validation is finished.
- Start the intended writers and check the saved historical sessions, aggregate view and a new controlled test session. Review logs for failed reads or writes.
Check the result
Historical and new records should appear in the same intended dashboard without duplicate server identities. Compare selected session dates and durations with the pre-change notes. A successful database connection proves access, but does not establish that the old analytics were transferred.
If the result differs
If history is absent, stop further migration attempts and inspect which source was transferred and which destination the interface reads. If only new sessions appear, do not overwrite the original database with the empty destination. Keep credentials out of support excerpts.
Return writers to the recorded original configuration if validation fails, taking care not to lose sessions created during the trial. Preserve both checkpoints for a deliberate reconciliation. Do not delete the old database or rebuild analytics merely to hide a migration mismatch.
