Harrowell service

OJS/PKP migration

Move a journal into Open Journal Systems through a controlled publishing migration that protects data integrity, workflow readiness and continuity.

The service in context

Practical support for a connected publishing operation.

An OJS/PKP migration is a publishing transformation, not simply a technical transfer. It brings together journal settings, article content, files, users, roles, metadata, editorial workflows, integrations and the expectations of the journal community. Harrowell manages those dependencies as one coordinated project.

A platform move can create avoidable risk when data is not fully inventoried, workflow decisions are postponed or validation happens too late. Our approach makes the migration scope, mapping, checks, acceptance criteria and go-live responsibilities visible from the outset.

What the service includes

The capabilities behind the service.

Every engagement is scoped around your journal’s needs. These are the core areas Harrowell can bring together in this service.

Migration discovery and inventory

Identify journal content, files, users, permissions, metadata, settings, workflows and integrations that need to be understood before migration.

OJS configuration and workflow design

Configure journal structures, roles, editorial stages, communications and publication settings around the journal’s intended operation.

Data mapping and validation

Map legacy information to the OJS environment and establish test, review and acceptance checks for content, metadata, files and user records.

Go-live and stabilisation

Coordinate launch communications, operational handover, issue resolution and post-migration review so the journal moves into a stable service model.

Where we add depth

Designed around the realities of scholarly publishing.

Harrowell can take responsibility for a complete workstream or strengthen the part of an existing operation that needs more structure, capacity or specialist attention.

A full publishing inventory

Before any move, we establish what the journal has and how it works. This prevents important records, dependencies and workflow decisions from being discovered only at the point of go-live.

Article, issue, file and backfile inventory
Users, roles and permission review
Metadata, identifiers and integration register

Test before launch

Migration quality is demonstrated through a staged process. We support test migration, content and data validation, workflow checks and agreed acceptance criteria before the production environment is released.

Test migration and exception log
Editorial and publishing workflow validation
Acceptance checklist and readiness review

Continuity after go-live

A successful launch is the beginning of the new operating environment. We support user handover, early-stage service monitoring and practical adjustments as the journal settles into OJS/PKP.

Go-live communications and support
Operational handover documentation
Post-migration stabilisation review

How we work

A structured path from need to delivery.

The pace, scope and ownership are agreed around your journal. We make the work visible and give editorial, operational and organisational stakeholders a clear role throughout.

Establish the migration scope, inventory and continuity requirements
Configure OJS/PKP and map content, metadata, users and workflows
Run test migration, validate results and resolve exceptions
Manage controlled go-live, handover and stabilisation

What is agreed up front

A service with visible ownership.

Every engagement begins with an agreed scope, responsibilities, review rhythm and practical definition of delivery. This makes it clear what Harrowell is accountable for, where decisions sit and how the work connects to your wider publishing operation.

Migration inventory and mapping register

OJS/PKP configuration and workflow plan

Validation, acceptance and go-live checklist

Post-migration review and handover pack

What this makes possible

The outcomes a stronger service model should create.

A documented and validated OJS/PKP migration
Stronger confidence in content, metadata and user-record integrity
A platform configured around real editorial and publishing workflows
A clear operating handover after launch

A good fit when

Journals moving from another platform into OJS/PKP, publishers modernising a portfolio, and societies or institutions establishing a dependable open-source publishing environment.

Harrowell can provide this as a focused project, an ongoing managed service or part of a wider publishing partnership. The scope is shaped around the journal’s current operation, priorities and development plans.

Discuss your requirements

Build a service model around the work your journal needs to do next.

Tell us about the journal, programme or operational challenge. We’ll help identify the right starting point and delivery model.

Start a conversation →