A Journal’s Biggest Data Migration Isn’t the Manuscript: How to Switch Peer-Review Platforms Without Losing Editorial History

A migration plan for preserving decisions, reviewer records, manuscript versions, permissions, and the audit trail

A Journal’s Biggest Data Migration Isn’t the Manuscript: How to Switch Peer-Review Platforms Without Losing Editorial History

A journal platform migration raises a familiar question: when a journal changes peer-review platforms, the most visible concern is usually the manuscript file. Can the new system store the PDF, Word document, figures, and supplementary data? That is necessary, but it is not the difficult part. A journal’s editorial history is distributed across people, events, decisions, correspondence, reviewer invitations, revision cycles, forms, and permissions.

The risk is real because a peer-review platform is not simply a document repository. It is a workflow system and a record of editorial activity. Crossref’s platform-migration guidance recommends beginning with a metadata audit, planning DOI and URL updates, and asking vendors detailed questions about the content and metadata they can support [1].

Map the editorial record before exporting data

Start by inventorying what the current platform stores. A submission may include the original manuscript, revised versions, figures, supplementary files, author metadata, affiliations, funding statements, declarations, reviewer suggestions, editor assignments, reviewer invitations, acceptances and declines, reviewer reports, decision letters, and correspondence. It may also contain workflow events such as technical checks, plagiarism screening, ethics queries, transfer offers, revisions requested, and final decisions.

The relationships between these records matter as much as the records themselves. A reviewer report must remain linked to the correct manuscript version and review round. A decision letter must remain associated with the editor who issued it and the evidence available at that time.

Classify records and define the platform migration boundary

Not every record should be migrated in the same way. Divide the journal’s data into active submissions, accepted manuscripts awaiting production, recently completed decisions, rejected or withdrawn submissions, and older archived records. Define which groups must remain fully searchable in the new platform and which can be retained in a secure read-only archive.

Create a data dictionary that maps every source field to a target field or an explicit disposition. Record whether a field is mandatory, optional, confidential, user-visible, or used in reporting. Pay special attention to status codes. “Awaiting reviewer reports” and “awaiting editor decision” are not interchangeable, even if a vendor’s target system uses different labels.

Protect manuscript identity and version history

Every submission should retain a stable identifier or a reliable cross-reference between the old and new identifiers. Preserve the complete version sequence, including dates, filenames, and relationships to review rounds. Do not overwrite an earlier manuscript when a revised file arrives. Editors may need to compare versions to understand whether author responses addressed reviewer concerns, and an audit or complaint may require the original material.

Test supplementary material and related files as carefully as the main manuscript. Check whether images, datasets, ethics documents, consent forms, reporting checklists, and conflict-of-interest declarations remain attached to the correct version. Validate file readability, naming, access restrictions, and integrity. For confidential peer-review files, use controlled transfer channels and restrict access to authorised migration personnel.

Preserve reviewer, editor, and correspondence history

Reviewer records are especially sensitive. The platform migration should retain invitation history, acceptance or decline status, deadlines, completed reports, recommendations, score sheets, and the identity or pseudonymous reference of the reviewer according to the journal’s review model. Do not convert an anonymous review into an identified review by accident.

Correspondence also needs context. Preserve who sent a message, who received it, when it was sent, which manuscript version it concerned, and whether it was an automated notification or a decision communication. Wiley’s publicly described Research Exchange migration process provides a practical example: it explains that reviewer data and reports are transferred, and that in-flight manuscripts can carry their manuscript history, original IDs, and reviewer history into the new platform [3].

Design an in-flight manuscript strategy

Active submissions are the most operationally sensitive group because authors, reviewers, and editors may be working in the system during platform migration. There are several possible strategies: migrate all active records on a fixed cutover date; keep some records in the old system until a defined milestone; or operate a temporary dual-system process for a limited period. Each approach has trade-offs.

Before cutover, agree a submission freeze or controlled delta-capture window. Export a baseline dataset, record the time of extraction, then capture any new decisions, reports, or status changes made after that point. Define how last-minute events will be reconciled. The publisher should tell editors and authors which platform to use, how reviewer invitations will be handled, and where support is available.

Validate the platform migration with evidence

Do not sign off because the vendor says the import completed. Reconcile record counts by journal, year, status, and review stage. Compare the number of manuscript versions, reviewer reports, decisions, correspondence items, and attachments. Use file hashes or other integrity checks for transferred documents where practical.

Run role-based tests. An editor should see the correct reports and decision history; an author should see only information permitted by the journal’s review model; a reviewer should see the assigned files and relevant instructions; and an administrator should be able to investigate an audit trail. Check reports and exports as well as screens.

Protect the DOI layer and long-term access

Moving the peer-review system does not always mean moving the journal’s hosting platform, but publishers often change both systems during a wider modernisation project. Treat DOI resolution and content hosting as a separate workstream. Crossref advises publishers to audit existing metadata, check the new provider’s ability to deposit rich metadata, and coordinate URL updates when a platform moves [1].

Confirm which platform owns the DOI credentials, who may deposit or update metadata, how redirects will work, and how back-year content will be supported. Ensure that the new provider can preserve abstracts, references, ORCID iDs, funding data, licence URLs, and other metadata the publisher currently deposits. Keep an archive or preservation arrangement for published content.

Put migration requirements into the vendor agreement

A platform migration statement of work should identify the data scope, export format, mapping responsibilities, treatment of attachments, handling of in-flight manuscripts, test cycles, reconciliation reports, security controls, rollback criteria, and post-launch support. The contract should say who corrects failed records, who pays for rework, how long the old environment remains available, and when data is securely deleted after the agreed retention period.

Use the platform migration to improve data quality, but do not silently rewrite history. It is reasonable to normalise inconsistent affiliation labels or map equivalent status codes if the original value and mapping are retained. It is not reasonable to erase a decision, change a timestamp, or merge reviewer identities without a documented basis.

Illustrative scenario: a publisher moves twelve journals to a new platform

A publisher is replacing its peer-review platform across twelve journals. A first export appears complete because every manuscript ID and main document is present. During a pilot, however, an editor discovers that two revision rounds have been flattened into a single record, and completed reviewer score sheets are not visible to the editorial office.

The team then tests three in-flight manuscripts, one accepted manuscript, one rejected submission, and records from an older year. Counts are reconciled, permissions are tested for editors, authors, and reviewers, and the old system remains read-only until the journal managers sign off.

Conclusion

A journal platform migration succeeds when it preserves the story behind every editorial decision—not merely the manuscript file. Map the data, retain version and reviewer relationships, protect confidentiality, plan in-flight work, test role-based access, and reconcile results before switching off the old system. Treat DOI and hosting changes as connected but separate workstreams.

Frequently Asked Questions

Which data is most important to preserve in a peer-review platform migration?

At minimum: manuscript versions and files, submission metadata, reviewer invitations and reports, editor assignments, decision letters, correspondence, status history, and audit events. Preserve the relationships between these records, not just the individual files.

Should all historical manuscripts be imported into the new system?

Not necessarily. Active and recent records may need full workflow access, while older records may be retained in a secure read-only archive. The decision should follow retention, privacy, audit, and operational requirements.

How should in-flight manuscripts be handled?

Define a clear cutover strategy, freeze or capture changes at an agreed time, and specify where authors, reviewers, and editors should continue their work. Test each review stage before platform migration.

Do article DOIs need to change when a peer-review platform changes?

Usually not. A peer-review-system change alone does not require new article DOIs. If the published-content URL changes, update DOI resolution URLs and metadata as appropriate, following Crossref guidance.

How can publishers verify that the migration is complete?

Reconcile record and attachment counts, compare versions and reviewer histories, test access permissions, sample every workflow status, verify reports and exports, and obtain sign-off from editorial users.

What should a publisher ask a new platform vendor?

Ask for sample exports, supported data fields, mapping documentation, treatment of in-flight records, security controls, audit-trail retention, DOI and metadata support, backfile handling, testing responsibilities, rollback plans, and post-migration support.

Sources and Further Reading

1. Crossref, Planning a platform migration

2. Crossref, Checklist for platform migration

3. Wiley, Research Exchange Help and Support — migration and legacy data

4. Crossref, Transferring titles and identifiers to a new owner

5. Crossref, Updating your metadata

6. Sage, Submission management in Sage Track

Journal publishing, weekly

Keep up with the conversations moving journals forward.

Peer review, research integrity and journal operations, examined for editors and societies.

No spam. Just meaningful updates.