It is not acceptable that we must manually re-enter all our schedules because your new scheduling system cannot transfer data from the old one. Forcing customers to redo everything due to poor data migration is unreasonable.
Please provide a solution to import our existing schedules.
""""""""""""" "
Updated FAQ's on scheduling migration
Hi everyone! 👋
We understand that migrations can be tricky, particularly when they require manual work on your end — we hear you, and we want to make sure you feel supported throughout this process.
We've also received a lot of messages and feedback lately — thank you for taking the time to share your thoughts. We've been reading through everything and have updated the FAQ section to address the most common questions we've seen come through. We'd recommend giving it a look as it may already have the answer you're after.
A couple key updates I want to call out:
📅 The new public API for Scheduling will be published on April 8th.
🔔 We have not yet started the deprecation process for the legacy Scheduling feature. When this begins, we will provide direct comms to admins so you have plenty of notice and time to prepare.
"