Purpose
This guide outlines the process for migrating a client's pension provider from NEST to Jarvis. While technically applicable to migrations from NEST to any provider, this guide focuses specifically on NEST-to-Jarvis transitions.
Pre-Requisites
Before starting the migration, ensure:
Payroll completion
All payroll for the current week must be complete
Execute migration at week-end (Friday evening) OR week-start (Monday before corrections)
Timing for corrections
If you typically perform Monday morning rollbacks/corrections, wait until these are complete
If corrections happen throughout the week, be aware that NEST-period corrections must be handled manually in NEST Portal after migration
Worker communication
Notify all pension-enrolled workers of the provider change
Advise workers to expect a Jarvis welcome email on the migration date
CRITICAL
Complete all known payroll corrections before proceeding. Corrections to NEST-period contributions after migration require manual intervention.
Phase 1: Cease NEST Contributions
Objective
Notify NEST that no further contributions will be submitted. Without this, NEST will flag missing contributions to employees and escalate to the Pension Regulator.
Why Extract First
Extracting active employments before ceasing allows clear identification of workers who need Jarvis enrolment, versus those legitimately ceased outside of migration.
Steps
Enable Jarvis Pension on the Pension Configuration screen in Finity
Extract all employments with active enrolled pensions
Store in spreadsheet for Phase 2 reference
This becomes the migration list
Cease all active pensions on the Finity platform with effective date = last Friday
Submit final NEST contributions to bring account current
Standard schedule: Typically Monday submission, 2 weeks in arrears
Migration requirement: Raise contribution schedules for final 2 weeks to close NEST account
WARNING - TIMING COORDINATION: If NEST contributions are submitted before Step 3 is complete, workers must be marked as leavers, then a CSV must be manually exported for the current week (showing £0 contributions + "Cease" flags). This creates exceptions and should be avoided. Coordinate timing carefully—do NOT submit final contributions until Steps 1-3 are complete on the Finity platform.
Manually trigger NEST contribution processing in Finity
This avoids overnight processing delays
Resolve any NEST errors and mark for re-submission
Coordinate with Finity support to re-trigger scheduled tasks
Avoid overnight processing delays
Success Criteria
All NEST contributions submitted and accepted
All active workers flagged with cease dates
NEST account brought current with no outstanding submissions
Phase 2: Enrol Workers into Jarvis
Objective
Migrate pension enrolment data from NEST to Jarvis while preserving worker statuses.
Steps
Archive NEST contribution history on the Finity platform
A script will store NEST contributions in an archive table
This preserves historical data for reference
Re-activate pension records for all previously active enrolments
The Finity platform will reset enrolment status with the following rules:
Opted-out workers remain opted out
Ceased workers remain ceased
Deferred workers remain deferred
Opt-out window end date set to last Friday (newly enrolled workers have no opt-out period)
Change employer pension provider to Jarvis in Finity
The system automatically updates pension communication templates
Generate and submit enrolment file for migrated workers
Extract enrolment data for workers identified in Phase 1, Step 2
Upload to Jarvis portal
Alternative process: Some clients receive a dedicated SharePoint folder from Jarvis for first enrolment upload. This allows Jarvis to validate files before processing. Following validation, upload manually to the Jarvis portal.
Success Criteria
All previously active workers enrolled in Jarvis
Worker statuses correctly preserved (opted out, ceased, deferred)
Enrolment file successfully uploaded to Jarvis portal
Phase 3: Submit Contributions
Objective
Resume normal contribution schedule with Jarvis as new provider.
Timeline
Standard schedule: Contributions submitted 2 weeks in arrears
First Jarvis contributions: Due 2 weeks after migration date
2-week arrears recommended to allow for payroll corrections
Exception Handling
NEST Correction Period
Rollbacks or corrections for workers with NEST pensions (i.e., the most recent 2 weeks before migration) require manual intervention:
Raise manual exception schedules in NEST, OR
Manually adjust in NEST portal (if payment not yet taken)
Recommendation
Avoid rollbacks during the 2-week migration period where possible.
Normal Operations Resume
Process payroll as normal
Submit Jarvis contributions 2 weeks in arrears using the Finity platform
Monitor for any migration-related issues in first 2-3 submission cycles
Success Criteria
First Jarvis contribution schedule submitted on expected timeline
No outstanding NEST corrections or exceptions
Normal payroll cycle resumed
Post-Migration Verification
Within the first 2 weeks after migration, verify:
All workers from the extraction list successfully enrolled in Jarvis (check Finity platform)
NEST account shows no outstanding contribution schedules (check Finity platform)
Workers received Jarvis welcome emails
First Jarvis contribution file generated successfully
No orphaned pension records in the Finity system
NEST portal shows account closed with no further contributions expected
Support
For migration assistance:
Contact Finity Support Team
For Jarvis-specific queries: [email protected]