Sign In
Get a Demo

In our experience, it takes customers 2 - 4 weeks to switch to Sapling as their employee experience platform.  For customers with employees of 1,000 or more, the time-to-complete the migration is closer to 4 - 8 weeks.

Sapling's Customer Success Team will be dedicated to making sure that you have the support you need to for a successful transition to Sapling. 

There are three stages covered in the migration process.


Stage #1 - Account Review

The Sapling team will conduct a review of your existing data and system, including:

  • What employee data is being stored?
  • What employee activities are managed through the system (tasks, documents, time off etc.)?
  • What are the key workflows of different stakeholder in the platform?

This is typically best achieved through sharing access credentials of a Super Admin (or setting an account up for Sapling’s implementations team).

Stage #2 - Implementation 

Your Customer Success Manager will then take your company data and spreadsheets, migrate them into the Sapling system, and then provide login credentials to Sapling.

This will include all of your employees’ personal and role information, as well as additional and private information such as compensation data and emergency contacts.  

Next, we help customize the system including documents, tasks, emails and your employee record set-up.

Stage #3 - Communication + Roll Out 

Communication is the key to success of any new software implementation; so we make sure to support your to train key stakeholders and provide clear expectations as to what is expected of them.

We suggest that you conduct basic training for key users, including giving some employees access so they can review their information and conduct an employee-level review the new platform.

Once confirmed, Sapling will then bulk send invitations to your team.

While Sapling will always be designed to be simple and intuitive for your team, it often helps to point your team  to Sapling overviews for New Hires and Employees or Managers for their role-based learning path.