Data migration
So you can keep working seamlessly from day one, we migrate your existing data — regular guests, future bookings, outstanding invoices, optionally your booking history. Our goal is that on go-live day no guest notices a difference: in-progress bookings are visible, regulars are recognised, invoices can be closed.
What we migrate
Section titled “What we migrate”| Data type | Standard | Optional |
|---|---|---|
| Guest master data (address, contact, date of birth) | yes | — |
| Preferred pitch | yes | — |
| Future bookings (confirmed and tentative) | yes | — |
| Deposits for future bookings | yes | — |
| Outstanding invoices | yes | — |
| Historical bookings | no | yes, for occupancy stats and returning-guest logic |
| Marketing consent | only with proof | yes |
| Season cards / long-term campers | yes | — |
| Tourist-tax configuration | yes | — |
| Notes on guest profile | yes | — |
What we do not migrate: photos, T&Cs, marketing copy. These get reset in the branding step of setup — usually a welcome chance to refresh them.
Supported source systems
Section titled “Supported source systems”We have migration scripts for the systems common in Switzerland:
- CampSoft (Microsoft Access based)
- Compusoft Camping
- easycamp
- Camping Manager (DOS-based, older versions)
- Lobbi PMS
- custom Excel and Access lists
- generic CSV exports (e.g. from in-house solutions)
If your system isn’t listed: send us a sample export, we’ll check the structure and come back with an approach.
Process
Section titled “Process”Phase 1: Trial run
Section titled “Phase 1: Trial run”You export your data — we send a step-by-step guide per system. The export goes through an encrypted upload (no e-mail attachment). We import the data into a sandbox tenant and report:
- count of records found per type
- detected duplicates (e.g. the same e-mail with two spellings)
- missing mandatory fields (e.g. a booking with no pitch assignment)
- inconsistent data (e.g. cancellation date before booking date)
You review a sample and decide together with us what needs cleaning.
Phase 2: Cleanup
Section titled “Phase 2: Cleanup”Common cleanup steps:
- deduplication by e-mail + name + date of birth
- typos in addresses (postcode, country)
- stale contact data (bouncing e-mails marked “undeliverable”)
- category mapping of old guests to your new pitch types
- cancellation status for definitively cancelled bookings
We do most of it; you review your top regulars and correct known inconsistencies.
Phase 3: Final import
Section titled “Phase 3: Final import”Once cleanup is approved, we run the cutover — typically in the evening after end of business. We freeze your old system, export final data, import into CampOne, and switch on production. Cutover takes 1–4 hours depending on data volume.
If your old system can’t go offline (e.g. because an online widget keeps running), we run a delta import for any bookings created between trial run and cutover.
Data protection and security
Section titled “Data protection and security”- Transfer is exclusively encrypted (TLS 1.3, optionally PGP on top)
- Data is processed in an isolated sandbox tenant, not in production
- Access only by the migration team, logged in the audit trail
- Sandbox data is deleted automatically 90 days after go-live
- You sign a data processing agreement that explicitly covers migration
Data quality: what you should check yourself
Section titled “Data quality: what you should check yourself”Every old system has data-quality issues. Before the trial run it helps if you:
- review and correct the primary contact record for your top-50 regulars
- clean up open “orphan” bookings (old bookings with no status)
- standardise duplicate pitch names
This prep pays off twice — clean migration and clean follow-on years.
How long does migration take?
With clean source data, 1–2 weeks. With messy or scattered data (Excel + Access + paper), 3–5 weeks.
Can we start with an empty system and load data later?
Yes. Some sites deliberately start with master data and future bookings, then add history once the team has settled in.
Will Booking.com bookings be carried over?
Yes, as long as Booking.com still has visible future bookings at go-live — we import via Booking.com’s own export or the channel manager.
What happens to our old software after go-live?
You keep read-only access for an agreed period (often 12 months) for evidence and old invoice queries. Write access is disabled at cutover.
- Take the sandbox seriously. The trial run is the last chance to catch data-quality issues before they go live.
- Plan migration, don’t improvise. Set the cutover date early and block 24 hours after it without booking traffic.
- Keep backups. Hold a full backup of your old database for at least 7 years — even after the software stops running.