Internal Transfer Onboarding Plan — Team Integration & 30-60-90 Ramp

This template is built for internal transfers, not brand-new hires. It assumes the employee already knows your company’s tools, policies, and culture, so the focus shifts to the new team’s expectations, workflows, and relationships. If you need a first-time employee onboarding flow, use a new-hire onboarding template instead.

Use it every time someone moves to a new team, whether the move is lateral, a promotion into a new function, or a transfer after reorganization. The plan typically runs across 30, 60, and 90 days, with check-ins at each milestone. For highly regulated or technical roles, you may add an earlier Day 1 compliance checkpoint.

The receiving manager should own the plan, with support from HR, the prior manager, IT, and any team buddy or mentor. The manager is responsible for role clarity, goals, and feedback cadence, while HR and operations handle access, documentation, and required training. This division keeps the plan from becoming a vague handoff instead of a real ramp.

Include any updated role documentation, revised job description acknowledgment, access re-provisioning, and role-specific training that applies to the new team. If the transfer changes systems, data permissions, or regulated responsibilities, the plan should capture those changes immediately. For some roles, that may also include safety, privacy, finance, or security training before the employee begins independent work.

A standard 30-60-90 plan often focuses on a new hire learning the company from scratch. This template starts from the assumption that the employee already has institutional knowledge and instead targets team-specific clarification, culture, and connection. That makes it better for internal mobility, where the main risk is not ignorance of the company but misalignment with the new team.

The biggest mistake is treating the transfer like a simple desk move and skipping manager handoff, access changes, and goal reset. Another common issue is leaving the employee with two sets of expectations from the old and new teams. This template helps prevent that by making ownership, milestones, and communication norms explicit.

Yes. You can adjust the 30-60-90 milestones, the amount of orientation time, and the depth of stakeholder mapping based on role level. Entry and mid-level transfers usually need more process clarification, while senior transfers often need more cross-functional alignment and skip-level connection.

Common handoffs include HRIS updates, IT access changes, manager task lists, learning assignments, and calendar invites for introductions and check-ins. If your team uses project tools or OKR systems, link the plan to those records so goals and follow-ups stay visible. The template works best when it is connected to the systems that already track access, tasks, and performance.