Now, let’s get your team on board! To make this transition as quick and pain-free as possible, take this proven process and memorize it by 🧡
Step 1: Plan a day’s worth of content in CoSchedule.
To kick things off, plan out at least one day’s worth of social messages, blogs, projects, campaigns, and tasks inside CoSchedule. Include everything your team is working on. You want to showcase how CoSchedule will look (and function) for your team.
<IMAGE: A calendar view with a week’s worth of content on it.>
Step 2: Update settings in CoSchedule to make the transition from Basecamp feel familiar.
Add color labels (color coding) and tags (categories) in CoSchedule to mirror the ones you used to categorize projects in Basecamp.
<GIF: Update Color Labels in Calendar Settings.>
Create task templates with the same workflow your team is using in Basecamp. Build out task templates for any recurring project type your team creates, i.e. blog posts, events, email campaigns, etc.
<GIF: Save a new task template.>
Step 3: Schedule a team meeting.
The next step is to demonstrate the value of CoSchedule. Demo the features and highlight your team’s new project workflow to get everyone on the same page.
Pro Tip: Want to get a better turnout? Entice your team by ordering coffee for this meeting (on us!). Contact your customer success manager, and we’ll make sure your team is caffeinated and ready to learn.
After this meeting, your team will be ready to jump in head first! But with major change comes the chance a few employees may struggle with the transition. Because you know, “this is the way we’ve always done it.”
And you don’t want to leave them on the sidelines.
Step 4: Move work into CoSchedule (ASAP).
To phase out Basecamp, we’ve outlined two game plans for you. Choose the option that works best for your team size and workload.
1) Run out the current projects in Basecamp - Post meeting, no new new projects get added to Basecamp. Anything new on your roadmap gets added to CoSchedule right away. When there are no remaining projects in Basecamp, you can officially retire it!
- You don’t have to transition any existing projects from Basecamp to CoSchedule.
- Your team has to use two tools simultaneously to manage projects, which decreases efficiency + increases risk for miscommunication.
- You will likely have a longer transition period - making it more difficult for resistant team members to adopt CoSchedule.
2) Transition all projects to CoSchedule - This option is a clean break. And your team won’t have to recall which projects live inside which tool.
To do this, set a hard deadline for your team. All projects will be required to live in CoSchedule as of December 1 (for example). After your deadline, there will be no access to Basecamp.
- You have very defined expectations for your team’s transition plan.
- You know the “end date” for Basecamp; making it easier to cancel your previous plan.
- Your team only uses one tool for managing projects.
- Old projects need to get transitioned from Basecamp to CoSchedule, which takes time and resources to update.
Regardless of which option you choose, make sure to clearly communicate expectations and timelines to your team.
Continuously share the value of using CoSchedule vs. Basecamp. Utilize your customer success manager for support through the process as needed. And don’t forget to share CoSchedule’s help docs for additional resources.