Home/Migration and onboarding
TrustMigration and onboarding
Moving a live review process is the part most vendors gloss over. Here is what actually happens, including the parts that are inconvenient.
Last reviewed August 2026
The questions we are asked first
Written so this section can be copied straight into a security questionnaire.
Four steps, and the third one is the honest part
Push the revisions through
Write to authors holding manuscripts for revision and ask them to expedite. Most will resubmit and reach a decision in the old system, which removes them from the problem entirely.
Take your reviewer records out
Export reviewer names and their completed reviews from the old system before the contract ends. This is the part people forget, and it is the part that cannot be recovered afterwards.
Whatever is left resubmits
The author creates an account and submits as new, including their response to reviewers. A flag marks it as a resubmission, so it is easy to spot in a queue and easy to exclude from reporting.
New submissions open in PeerPath
From a date you choose. The old system finishes what it started and then closes.
Why we do not migrate reviews in progress
A review in progress is not a file. It is a set of invitations, deadlines, permissions, blinding rules and states that only make sense inside the system that created them. Rebuilding that faithfully in a second system is slower, more fragile and easier to get quietly wrong than finishing it where it started. So we say finish it there, and start clean here.
What we configure with you
| Workflow | Editor levels, stages, and the roles your process actually uses. |
|---|---|
| Submission forms | One per article or grant type, with your fields, your help text and your rules. |
| Email templates | Every message, in your wording, with the versions you need. |
| Staff and permissions | People, roles, and who recommends against who decides. |
| Reviewer database | Imported from what you were able to export. |
| Integrations | Whichever you already hold a subscription for. |
What we need from you
| A switch date | The day new submissions start arriving in PeerPath. |
|---|---|
| A configure manager | One person who can make decisions about how the process should work. |
| Your guidelines and templates | So the wording is yours from the first day rather than ours. |
| Your staff list | With roles, so permissions are right before anyone logs in. |
| Reviewer records | Exported from the old system while you still have access. |
- Manuscripts already out for review are best finished in the old system.
- We do not store legacy files from a previous system.
- Reviewer records can only be exported while your old contract is still live. Nobody can recover them afterwards.
Tell us what you review.
We will show you the workflow.
Send us the outline of your process and we will build it in a session with you.