
Old Slip Insights · Retirement Plans
November 21, 2026
Moving a 401(k) plan to a new recordkeeper is an operational project with consequences for employees, payroll, and fiduciary oversight. In this Old Slip Insights note, we outline how CFOs and HR leaders can organize the transition, identify gaps before assets move, and confirm that the new arrangement works as intended.
A recordkeeper conversion involves more than transferring account balances. Participant records, investment elections, outstanding loans, beneficiary information, and payroll instructions may travel through different systems on different schedules. Start with a written project plan that identifies each workstream, its internal owner, the responsible provider, and the evidence needed to mark it complete.
Designate one internal transition lead, usually in HR or benefits, with a CFO-level escalation contact. Include payroll, the outgoing and incoming recordkeepers, the third-party administrator where applicable, and the plan’s investment adviser. Do not assume that either recordkeeper owns every task; responsibilities should be confirmed in writing.
Build the schedule around payroll dates, pending distributions, required notices, and the availability of staff who can resolve exceptions. Ask the outgoing provider about termination requirements and access to historical records after departure. The conversion date should follow a workable sequence, not simply an appealing month-end target.
An asset transfer can balance at the plan level while individual records remain incomplete or incorrect. Before conversion, request a data specification from the incoming recordkeeper and compare it with what the outgoing provider will deliver. Identify fields that require manual work and agree on who will resolve missing or conflicting information.
Pay particular attention to records that affect taxes, distributions, or employee rights. A participant’s total balance is not enough if the new system cannot distinguish the underlying contribution sources. Use secure transfer methods, limit access to people who need it, and retain an exception log with an owner and resolution for each issue.
A new recordkeeping platform may require different payroll codes, file formats, or approval steps. Even when providers describe the connection as automated, the employer should understand what information moves, when it moves, and who reviews rejected records. Test the connection before relying on it for a live payroll.
Use representative situations rather than only straightforward employee records. Confirm who maintains deferral elections during the changeover and how elections submitted near the cutoff will reach payroll. Loan repayments also need explicit treatment: the transition should not leave payroll withholding an amount that the new recordkeeper cannot identify or apply.
A conversion often requires deciding where existing balances will go and how future contributions will be invested. Those are related but distinct decisions. An employee’s current holdings may transfer under one mapping instruction while future payroll contributions follow another. Ask for a written explanation of both.
If the investment lineup is changing, the appropriate fiduciaries should review the proposed mapping rather than treating it as a routine systems setting. Consider investment objectives, risk characteristics, expenses, and any restrictions on moving assets. Do not assume that similarly named options are interchangeable or that every holding can transfer in kind.
Retain the approved mapping schedule, the rationale for material changes, and the participant communications describing them. Questions involving default investments, fiduciary protections, or required disclosures should be reviewed with qualified ERISA counsel. Operational convenience alone should not determine an investment decision.
During a conversion, participants may temporarily lose the ability to direct investments, request distributions, or take loans. This restriction is commonly called a blackout period. HR should know exactly which activities will be unavailable, when restrictions begin, and how employees will learn that access has resumed.
For plans subject to ERISA’s blackout-notice rules, advance notice is generally required at least 30 days, but not more than 60 days, before the last date participants can exercise the affected rights. Exceptions and detailed timing requirements can apply. Have qualified ERISA counsel confirm the applicable rules, notice content, delivery method, and response to any schedule changes.
Alongside required notices, provide a plain-English explanation of employee action items. Clarify whether new login credentials or elections are needed, where questions should go, and how pending requests will be handled. Avoid describing the transition as seamless; employees need accurate expectations, especially if they anticipate a distribution or loan.
The project is not complete when the new website opens. Establish acceptance criteria before the transfer and require written confirmation that balances, records, and payroll activity have been reconciled. Investigate discrepancies rather than assuming they reflect normal timing differences.
Schedule a post-conversion review after initial payroll processing and participant access have been tested. Keep unresolved items visible until they are corrected, and document any participant communication needed. The plan committee should receive a concise closing report that distinguishes completed work from remaining exceptions.
A documented conversion process helps CFOs and HR leaders coordinate providers without losing sight of participant needs. If your organization is considering a recordkeeper change, Old Slip Capital—an independent, fee-based registered investment adviser established in New York in 1966—welcomes a conversation about investment oversight and transition planning.