A 14-day, operator-supervised migration off Newbook. Your properties, sites, guests, reservations, ledger, and rate calendars — moved by a real engineer who has read your contract. Zero downtime, zero data loss, zero fee. The 30-day export window Newbook gives you? We only need two.
$1.50–$2.00/booking · 36-month lock-in · $550/property shared DB
$3/site flat · Month-to-month · Bring your own Stripe
Pulled from a real multi-property Newbook contract. If you're currently on Newbook, your contract almost certainly contains these same clauses. Here's how we handle each.
Cancel early and you owe "all payments made to date, plus the remaining balance of the term." A two-year-in cancellation can run into six figures for a 6-park chain.
After cancellation notice, you get 30 days to export. "Export fees may apply." After day 30, Newbook deletes — including historical reservations and ledger. That clock starts the moment you give notice.
The "shared guest database" fee. Charged per property you want to share guest records across. A 6-park chain pays $3,300 just to have one unified guest list.
Payments route through a Newbook-negotiated processor. Switching processors typically voids pricing. Card tokens are bound to that gateway — you can't export them.
Every booking and every text message is metered. SMS has a capped allotment with no rollover. A 92-site park doing 4,000 bookings/year quietly pays $6–8k on top of the base fee.
After the initial term, Newbook can raise your per-property subscription up to 20% per year. We've seen renewal notices land in January and take effect February 1.
45 minutes with your migration engineer. We read your Newbook contract together, flag the renewal date, and agree on a cutover window that avoids early-termination exposure.
Us + youYou trigger the full-account export from inside Newbook (Admin → Data → Export). We give you the exact click path. Full export runs overnight; you'll have the CSVs by morning.
You (10 min)We spin up a sandbox DwellSpace org that matches your production — one DwellSpace "park" per Newbook property. Rate calendars flattened, shared guest DB unified, edge cases surfaced.
UsWalk property-by-property through sitemap, guests, rate rules, refund policies. Red-pen anything that doesn't match reality. Most parks find 3–5 small things.
You (2–3 hrs)Two 45-min screenshare sessions. One for front-desk staff (check-in flow, payment processing), one for the owner/manager view (multi-property dashboard, reports). Recorded for the rest of the team.
Us + staffTake one new booking through DwellSpace production while Newbook stays primary. Payments route through your own Stripe. Proves the whole loop end-to-end.
Us + youStop accepting new bookings in Newbook. Existing bookings continue; we pull them forward to DwellSpace nightly.
You (10 min)Final Newbook export → DwellSpace production. DNS flip. Stripe webhooks reconnected. Shared guest DB deduped across all properties. Engineer on the phone the whole time.
Us + you (2 hrs)Engineer on standby for the first check-in shift. Once we've cleared 48 hours clean, you send written cancellation notice to Newbook. Your 30-day export window is already a non-issue — we pulled everything on day 1.
Us (standby)The honest version. Newbook's export is one of the cleanest in the industry — most of your data comes across without a hand on it. A handful of fields need human review; we flag each below.
/archive. Available for tax time.We had six properties on Newbook. The $550-per-park shared-database fee alone was three grand of our budget. DwellSpace pulled every property in thirteen days, deduped our guest list across all six, and our first month's bill was less than one property's old subscription.
Usually yes, but timing matters. Your contract has a renewal window — typically 90 days before term end — during which written notice exits cleanly. Outside that window, early termination means you owe remaining payments. On our kickoff call we read your contract together, pull the exact dates, and time the migration so cutover lands inside your notice window. We've never had an operator pay an ETF.
Non-issue with our flow. We export everything on day 1 of our migration, before you give notice. By the time your 30-day clock starts, you're already live on DwellSpace and Newbook has nothing we need. We keep a sealed copy of your full export for 7 years regardless.
Only to send written cancellation notice per your contract — usually one email to your account manager. We've never needed operator-to-vendor communication during the actual migration. Your data is yours; Newbook's terms explicitly grant you export rights in Clause 9.
Yes, one time, at their next stay. This is a limitation of how Newbook's preferred-gateway tokens are bound to the Newbook account — not something we can work around. We send guests a one-click secure card-update link in the confirmation email. Our adoption rate is 94% within 48 hours.
No — one migration, one timeline, one engineer. Each Newbook property becomes a DwellSpace park under a single org. Shared guest database deduplicated on import. Multi-property reports work from day one, no $550-per-park shared-DB fee.
They stay valid. At cutover we pull them into DwellSpace and send the guest a single, human-written email confirming nothing has changed for them. Confirmation numbers, stay dates, and payment stay exactly as they were.
Yes. Leave your website as-is and just swap the booking widget to DwellSpace. Or migrate to our website builder for free during onboarding. About 60% of operators switch; 40% keep their existing site.
We stop. You owe nothing. Your Newbook account was never touched, so there's nothing to revert. The engineer's time is our cost, and we've made peace with that.
An engineer. Specifically, a person who has shipped code to our Newbook import pipeline and has run at least 5 supervised Newbook migrations. That's the whole team — there are four of them — and you'll have one dedicated through day 14.
Per-booking fees, 2-year contracts, routed payouts. We handle the rate-plan flattening and the stored-token re-auth flow.
Campspot migration guide → RMS CloudCustom-field mapping and rate-grid flattening, both engineer-assisted. Still $0. Typical timeline is 18–21 days for parks over 200 sites.
RMS migration guide → Spreadsheets & pen-and-paperStill running the park from a Google Sheet? We've moved 34 parks from spreadsheets. Your data is usually cleaner than you think.
Spreadsheet migration guide →Kick off in the next 10 minutes. First call is 45 min, this week — we'll read your contract together.