Transfer history from an existing Nightscout site
Use the Nightscout data transfer tool to copy supported history between two live Nightscout sites. This is separate from Pro Connect’s continuing source connection.
Before submitting
The tool copies glucose readings (entries), treatments and profiles. It does not copy your old provider’s configuration variables or settings. Both the source and destination must remain live and accessible.
- Open the transfer tool and identify the old source and new destination carefully.
- Enter the requested site details and credentials only in the tool. Keep API Secrets out of support messages and screenshots.
- Select the intended history/collections offered by the form and submit the request.
- Keep the request/reference ID and submission time. Reconfigure your ongoing uploader separately to send future readings to the intended site.
How long it takes
A request can wait a few minutes to a few hours in the queue, depending on how busy the worker is. Once running, the worker normally transfers about 2–3 days of readings and treatments in a few minutes. That is a portion of the history, not the whole-job completion time. Total duration depends on the requested history and other jobs.
Stalled or uncertain progress
The worker sometimes gets stuck and needs manual support intervention. Contact support with the request ID if available, source/destination URLs, submission time, requested date range and status/error. Reuse details or screenshots already supplied.
Repeating the same transfer is duplicate-safe, as confirmed by Nightscout Pro. It does not clear a stuck worker or guarantee a repair. If progress has stopped or is unclear, have support inspect the existing job and worker before submitting again. This does not establish safety for arbitrary changes to the source, destination or requested range.
Job says complete but records are missing
Compare representative dates and collections at both sites. An online destination or current live glucose does not prove historical transfer completion. Ask support to inspect the existing job and the missing/incorrect date range and record types. A repeated identical transfer does not guarantee missing records will be repaired.
Support should only say a transfer was restarted, retried or completed when that action/result has actually been verified. Keep the source available until the needed history has been checked.