Book a demo

HomeResources › Migrating from Aptem to Journey: a practical provider checklist

Migration

Migrating from Aptem to Journey: a practical provider checklist

3 July 2026 · 2 min read · By Journey

Last reviewed: July 2026.

Changing apprenticeship software is never just a software decision. The risk sits in the learner record: ILR fields, off-the-job evidence, progress reviews, employer signatures, gateway status, audit history and the people who rely on the system every day.

This checklist is for providers comparing Aptem with Journey and wanting a safe migration plan. Aptem is a trademark of its owner; Journey is independent and not affiliated with Aptem.

Start with the records that must reconcile

Before any migration, define the fields that must reconcile between the old system, the ILR and the funding evidence pack. For apprenticeship providers this usually means learner identity, programme and standard, start date, planned end date, price, RPL adjustments, breaks in learning, actual end date, EPA status and achievement.

The migration should be tested against sample learners from different rule years, because a provider rarely has only one active funding rule pack in play.

  • ILR and funding fields
  • OTJ planned and actual hours
  • Progress reviews and actions
  • Employer and apprentice signatures
  • EPA gateway and outcome status
  • Audit trail and evidence attachments

Run a staged cutover

The safest migration is not a Friday export and Monday go-live for every learner. Start with a pilot cohort, reconcile funding and OTJ totals, check employer access, and confirm that tutors can continue reviews without re-keying historical evidence.

Once the pilot is signed off, move remaining cohorts in waves. Keep the old system read-only long enough to answer audit questions while the Journey record becomes the live source of truth.

Where Journey is different

Journey is designed around one audited apprenticeship record: MIS, e-portfolio, off-the-job tracking, ILR, funding, EPA and Ofsted-ready compliance on the same spine. That reduces the reconciliation burden that often appears when delivery evidence and funding data live in different places.

The migration goal is not to copy every screen from the previous system. It is to preserve the evidence and funding continuity providers need, then simplify the operating model around a single record.

Related reading

Journey is independent software and is not DfE or Ofsted approved. It does not guarantee funding or inspection outcomes.

Frequently asked questions

Can Journey import everything from Aptem automatically?

A safe migration depends on the available exports, data quality and the provider's history. The practical approach is to map core learner, funding, OTJ, evidence and user data first, then test a pilot cohort before a full cutover.

What is the biggest risk in an Aptem migration?

The biggest risk is losing reconciliation between the learner record, the ILR, OTJ evidence and the audit trail. A migration should prove those records match before the old system is made read-only.

See Journey in action

One audited platform for apprenticeship delivery, funding and compliance.

Book a demo