# Move to Business with your schedule and clients in order > Move to Reservation.Studio Business with data review, free transfer of the launch scope, and a staged rollout. Source: https://reservation.business/en/data-migration · Language: en Switching software should not stop the workday. We first review what can be exported from the current system, then move the data needed for a calm launch and widen the scope in stages. ## Migration works when the first live day is protected Not everything from the old system has to move at once. What matters first is the data the team needs to open the day with confidence: clients, services, team, upcoming schedule, and key notes. ## Migration happens in stages, not in one risky day The goal is for the team to start using Business with clear data and a protected schedule, without moving, checking, and learning everything on the same day. - **Review the source and the risk** — We review what can be exported from the current software, spreadsheet, or backup and which data is critical for the first live day. - **Confirm the launch scope** — We define what needs to go live first: clients, services, team, locations, upcoming schedule, or a specific part of the work. - **Import, review, and adjust** — We transfer the data, review the result, and clean up obvious gaps, duplicates, or mismatches before launch. - **Choose a go-live date and manage bookings** — We decide when the old channel stops accepting new appointments and when Business becomes the main system, so double bookings are avoided. - **Expand after the first stable launch** — After the first part is stable, we add deeper data, additional locations, modules, or more specialized needs. ## We start with the data that protects the workday The exact scope depends on what can be exported from the current software, spreadsheet, or internal process. That is why we review data quality and structure first, not only the name of the system. - **Clients, contacts, and important client context** — We move client records and the available context that matters for service delivery: contact details, notes, preferences, or history when they exist in a usable export. - **Services, team, locations, and core settings** — We set up the services, durations, team, locations, and settings that define how the business accepts and manages appointments. - **Upcoming schedule and the first part of the work that needs to run** — When the data allows it, we prepare upcoming appointments, important notes, and the first live day so launch does not create stress. - **Salons, beauty, and wellness**: Fresha, Booksy, Vagaro, Phorest, Treatwell, Zenoti - **Clinics, therapy, and practices**: Pabau, Cliniko, Noterro, Timify, SimplyBook.me, Reservio - **Studios and group activities**: Mindbody, Momence, TeamUp, Acuity Scheduling, Square Appointments, Setmore - **Non-standard sources**: Excel, Google Sheets, or CSV exports, Older local software, Mixed tools across several locations, Data exported by an external IT partner ## What makes migration predictable A calm migration has clear boundaries: what is available, what moves first, how it is checked, and which date makes the new system the main working system. - The transfer of the launch data you need to start with is free. - Before migration, we review what the current software or spreadsheet can export in a usable structure. - The first stage protects what matters most: clients, services, team, and the upcoming schedule. - The data is reviewed before go-live instead of discovering problems during the first working day. - Deeper or non-standard parts are added in stages once the foundation is stable. ## Frequently asked questions ### Is data migration really free? The transfer of the launch data you need to start using the system is free. If there is a lot of non-standard, detailed, or poorly structured data, we first clarify what can move cleanly and what needs additional cleanup. ### What should I prepare for the first review? The most useful starting point is an export from your current software, a CSV or Excel file, a services list, team and location information, and a short description of which part of the work needs to go live first. ### Can future appointments be migrated? When future appointments are available in a structured format, they can be part of the launch scope. If the source does not allow a clean export, we choose a safer approach with a go-live date and clear handling of the old and new booking channels. ### What does not move automatically? We do not blindly move payment data, external accounts, unstructured files, or fields that cannot be reliably connected to a client, appointment, or service. Those parts are reviewed separately. ### Do we need to switch everything in one day? No. The safer approach is to launch the core work first, then add more locations, modules, or deeper data after that base is stable. ## Related pages - [See the platform](https://reservation.business/en/platform) - [See solutions by business type](https://reservation.business/en/solutions) - [See pricing](https://reservation.business/en/pricing) - [Discuss migration](https://reservation.business/en/contact) ## Next step - [Discuss migration](https://reservation.business/en/contact) - [Book demo first](https://reservation.business/en/book-demo)