Your move to STRYK: checked first, then transferred.
You upload room types, rooms, companies, guests and bookings from your current system as files into one import job. We built the import so that STRYK suggests the mapping, shows every error and runs the transfer as a dry run before anything is written. With Easy Move by STRYK we plan the move together with you.

Multiple files
CSV, TSV, XLSX, JSON, NDJSON and ZIP in one job.
Dry run
You see in advance what would be created, linked or skipped.
Error report
Filter the messages and download them as an Excel report.
Easy Move by STRYK
Data migration, setup and team onboarding are part of getting started.
Bring your exports just as they come out of your old system.
An import job takes several files, Excel files with several sheets too, and STRYK never runs macros. The order of the files does not matter, STRYK checks the references between the tables. Keep the external IDs from your old system so STRYK recognises related guests, bookings and documents.
- CSV, TSV, XLSX and XLSM
- JSON, JSONL and NDJSON
- ZIP with several tables
- Excel templates with every supported field
Every column gets its target. You confirm.
STRYK suggests known field names, and for each sheet you check the target area and fields. STRYK offers confirmed mappings again for your next export from the same source system. Only what you confirm yourself becomes binding.
- Suggestions for known fields
- Reusable mappings
- Exclude sheets on purpose
- Replace a corrected file in the same job
You see errors before the import, not in the calendar.
STRYK reports missing details, invalid values, missing rooms and conflicting mappings. You filter by severity, field and error type and download the same selection as an Excel report. The dry run then shows what would be created, updated, linked, skipped or blocked.
- Every row checked
- Filter by severity and error type
- Excel error report
- Dry run before the transfer
After the import you compare before you switch over.
The follow-up area takes you to the open checks: numbers of guests, rooms and bookings against the old system, and spot checks on arrivals, rates and payment status. If the old system keeps changing, you run a targeted final sync at cutover, and STRYK never silently overwrites data you have already edited.
- Open checks and cutover sign-off
- Final sync at cutover
- Rollback check per imported record
- Import runs in the activity log


You do not make the switch on your own.
The hardest day is the first. That is why Easy Move by STRYK is part of your start: we set the scope and cut-off date with you, support data transfer, setup and team start, and check the results together. For STRYK Sites, our AI reads your existing hotel website and prepares the content as a suggestion with source references. Invoices and payments also go through a review by accounting.
- Agree scope and cutover date together
- Support with setup and team onboarding
- Content from your current hotel website as a suggestion
- Financial data with its own accounting checks
Four steps from file to hotel in STRYK.
We record every step in the same import job, so you can trace it.
- 01
Source
Upload files or connect a supported source system directly.
- 02
Mapping
Check and confirm target areas and fields.
- 03
Checks and dry run
Fix errors and preview the result.
- 04
Import and follow-up
Transfer, follow the progress and finish the spot checks.
Who works with it.
Owners and managers
Agree cutover date and scope with us and approve the transfer.
Reception
Checks future stays, room assignments and rates in the dry run.
Accounts
Reconciles open balances and financial data in the accounting checks.
Part of your complete system.
STRYK writes imported data straight into the areas your team works with from cutover day.
Common questions: Data migration
How does data migration begin?
With a personal migration review. STRYK agrees the data scope, cutover date and test cases with the property, reviews the source data and transfers it only after an approved dry run.
What is the goal of migration?
Bring rooms, guests, bookings and other required legacy data across under control without writing an unchecked file directly into live operations.
Which files can STRYK process?
CSV, Excel and structured ZIP packages with clear assignment to data areas. STRYK provides its own Excel templates for standard domains.
Which data areas can be transferred?
Rooms, categories, guests, bookings, status history, pricing, invoices, payments, POS context, channel references and guest photos, among others, within the jointly approved import scope.
What is an import job?
A bounded transfer run with source system, data area, files, mapping, checks, outcome and responsible person.
What happens after upload?
STRYK assigns tables and columns to the right property areas. Source values and prepared STRYK values appear side by side before the transfer.
Show more questions
What is field mapping?
Each source column is assigned to an appropriate STRYK field. Required fields must be confirmed before business validation continues.
Can STRYK suggest mappings?
Yes. STRYK suggests suitable target fields for recognised columns. The property confirms every mapping before data is transferred.
What does validation check?
Required fields, data types, relationships, duplicates, date logic, references and business conflicts for the relevant data area.
What happens on a blocker?
Dry run and productive import remain blocked until the issue is corrected or deliberately resolved.
Is there an error report?
Yes. The spreadsheet-compatible report identifies the row, field and specific issue so the property can correct errors precisely.
What is a dry run?
It simulates mapping and outcome without writing productive data. The property sees what would be created, updated, linked, skipped or blocked.
When may productive import run?
Only after confirmed mapping, successful validation, reviewed dry run and explicit approval by an authorised person.
Who may manage migrations?
Property users need a dedicated management permission; read-only access can see jobs, rows and logs but cannot start productive import.
Do original values remain visible?
Yes. Original value, STRYK preparation and row state remain traceable before and after the run.
How are duplicates prevented?
External IDs, business keys and conflict checks determine whether a record is created, linked, updated or blocked.
Can an import be rolled back?
Rollback review distinguishes safely removable imported objects from finance, POS, linked or subsequently changed data requiring manual correction.
Does rollback simply delete everything?
No. STRYK removes only clearly safe objects. Ambiguous or operationally reused records remain protected and are not deleted blindly.
Is import logged?
Yes. Job, mapping, dry run, transfer, outcome, failures and rollback remain traceable within the property and with a responsible person; central actions appear in the activity log.
Can I import arbitrary legacy data unchecked?
No. Migration scope is defined per property. Obsolete, legally unnecessary or operationally unclear data does not automatically belong in the new PMS.
How do I prepare a PMS switch?
Data scope, cutover date, owners, test cases and final work in the old system are defined before import. The detailed switching guide covers this preparation.
Is data migration included in the STRYK launch?
Yes. The safe migration path is part of personal launch planning. Scope, source data and exceptions are confirmed in advance; exceptional custom data preparation is commissioned only by transparent agreement.
Are there hidden migration fees?
STRYK has no hidden module or setup fees. Any exceptional custom data preparation or external partner cost is agreed transparently in advance.
Plan your switch with us.
Try STRYK for 14 days, or talk to us in a demo about your cutover date and data migration.