Visible data exchange, without pretending every connector is live
Use built-in ILR, calendar and versioned imports now, with tenant-scoped health and supported recovery; add external OAuth only after real approval.
Access checked at every layer.
Verified identity and provider membership
Role and record permission checks
Authorised reads and time-limited uploads
Bring learner profiles, ILR records and existing progress into Journey. Connect to Aptem read-only, map and preview the data, resolve duplicates, then approve a staged import. A native Meritura connection carries approved assessment packs to a connected assessment organisation and returns released results.
Move from Aptem with a preview you can inspect.
Connect to Aptem read-only and select a representative sample. Map programmes, inspect learner profiles and resolve duplicates in the preview before applying the import in stages. Controlled rollback supports the defined import operation.
Add existing learning progress through a mapped CSV: achieved KSBs, off-the-job hours, completed review counts and progress baselines. Historic evidence files and full review narratives follow a separate transfer. Your team reconciles the sample before expanding the migration.
Bring your data across with a clear plan.
Map learner details, employers, programmes and lifecycle states to the Journey record. Each import has a defined source, preview and validation step, so the team can check the data before it becomes part of live provision.
Moving from Bud, OneFile or another platform? Bring a representative export so we can agree the file mapping and migration plan. Applicant CSV and learner-progress imports cover their specified data.
Approve the pack. Continue in Meritura.
Journey prepares a versioned assessment pack for a connected assessment organisation using Meritura. A named person approves it. The native exchange tracks receipt, corrections and released results against the learner’s case.
The handover keeps the pack and its history connected across both platforms. The receiving organisation retains assessment and result-release decisions. The provider–assessment organisation connection is configured during onboarding.
What integrations does Journey support?
Journey supports ILR import and export, Aptem profile import, CSV learner-state import, an internal delivery calendar, versioned applicant CSV import and audited transactional email. External Google Calendar and Microsoft 365/Teams synchronisation is a separate capability to confirm in your implementation scope.
Are Google Calendar and Microsoft Teams connected in Journey today?
Journey’s built-in calendar connects delivery sessions, reviews, meeting details and resources. Google Calendar and Microsoft 365/Teams synchronisation are separate integrations; contact the team for current availability.
Brings together what used to be separate tools
Versioned Import Centre
Preview, map, validate and apply applicant CSV data while preserving provenance and guarded rollback.
Built-in ILR and calendar
Core ILR export and delivery scheduling work without an external calendar dependency.
Integration health
Directors can see status, last success, errors, recovery guidance and approval dependencies for their tenant.
Clear connection status
External OAuth, licences and customer-specific APIs stay unavailable until they are genuinely configured and tested.
Last reviewed: July 2026
See the status of every connection
See which services are connected, when they last succeeded and what needs attention. The connection register distinguishes built-in services, file exchange, recoverable errors and integrations awaiting approval.
Built so your team can trace evidence, decisions and actions
Tenant-scoped access controls
Tenant-scoped access controls are designed to keep each provider's records separate on reads and writes.
Controlled audit history
Significant application state changes are recorded against the person who made them, supporting a traceable history.
Published funding-rule packs
Journey applies supported, versioned DWP funding-rule packs selected from the apprentice's start date, including 2026/27 version 3, to support provider review.
Bounded AI assistance
Imports and integrations have their own permission and approval boundaries. A Journey AI answer can help explain recorded context; it cannot authorise a migration or release an assessment pack.
Evidence-led security controls
Tenant isolation, access controls, audit records and governed operations are designed into the platform.
Your data and employers stay yours
Export options are available under the applicable terms, and employer relationships remain with the provider.
Journey is independent software and is not DWP, DfE or Ofsted approved. It does not guarantee funding or inspection outcomes.
Questions providers ask
Can an import overwrite regulated data silently?
No. The applicant Import Centre creates a fixed preview first, applies once, records provenance and blocks rollback when records have since been edited or enrolled.
What happens when an external provider has no suitable API?
Journey uses a documented, versioned file contract with mapping, validation and error reporting rather than scraping or bypassing provider security.
Related pages.
See Journey on your own questions.
A guided walkthrough of the connected record and the questions your leadership team actually asks.
Bring the learner’s existing progress into Journey.
Journey has three connected import routes. Preview the data and resolve mappings before approving a transfer.
Aptem profiles
Connect read-only, sample the source, map programmes and review duplicates before applying the learner-profile import.
ILR records
Import apprenticeship learners, programme aims, employer links and funding source data. The preview identifies unsupported or skipped records before you apply the import. This brings records into Journey; it does not submit a funding return.
Learning progress
Import achieved KSBs, off-the-job hours, completed review counts and progress using a mapped CSV. The imported baseline lets your team continue from what the learner has already achieved. Historic evidence files and full review narratives need a separate transfer.
Review, apply and controlled rollback are part of the import workflow. See the migration steps with the Journey team.
Import information updated 11 September 2026.
See what changes
when it all connects.
Bring your learners’ journey, your team’s questions and your next ambition.