This is a working migration guide, not a sales page. It walks the actual sequence for moving a rental operation from 1Now to Rentovation, flags the two places operators lose data or bookings during a software switch, and is honest about the tradeoffs: 1Now has real strengths, and for some fleets it remains the better choice. If you want the full feature-by-feature and price-by-price breakdown first, start with Rentovation vs 1Now vs Fleetwire and come back here when you have decided to move.
Should you switch at all? The honest version
Reasons operators switch to Rentovation: a flat $197/month price with no vehicle cap(1Now’s published tiers cap at 10 and 25 cars before custom Enterprise pricing), a storefront and customer list you own outright, and built-in renter verification, e-sign agreements, and deposit holds on every booking (1now.ai/pricing, accessed July 21, 2026).
Reasons to stay on 1Now: if you run a hybrid operation and need Turo calendar sync, 1Now lists it and Rentovation deliberately does not build it; our product exists to move bookings off the marketplace, not to mirror it. And on published prices, 1Now’s $150/month Essential tier is cheaper than Rentovation below roughly 15 vehicles. If either of those is decisive for you, staying put is the right call and this guide ends here.
| Question | 1Now | Rentovation |
|---|---|---|
| Published monthly price | $150 (up to 10 cars), $260 (up to 25), Enterprise custom | $197 flat, no vehicle cap |
| Per-booking platform fee | $0 | $0 |
| Turo calendar sync | Listed | No (deliberate) |
| API access | Enterprise tier | See the comparison guide for the current integration story |
1Now figures: 1now.ai/pricing, accessed July 21, 2026. Rentovation figures come from our own live plan configuration. Verify current pricing on both sites before deciding.
Step 1: Export your data from 1Now
Before touching anything else, get your data out and into files you control. You want three exports, each as a CSV or spreadsheet:
- Vehicles (fleet export).The 1Now fleet export carries your vehicle names, specs, rates, and photo URLs in trailing image columns. This is the one file the importer is specifically tuned for: it recognizes 1Now’s vehicle-export column vocabulary on sight.
- Customers. Names, emails, and phone numbers. This list is the asset you have been building; do not leave it behind.
- Bookings. At minimum your current and future reservations, so the new calendar starts true. Past bookings are optional but useful for history.
If you cannot find an export button for one of these, ask 1Now support for a data export; reputable platforms provide one. Whatever you receive, keep the raw files. The importer maps columns visually, so an oddly shaped spreadsheet is a two-minute mapping job, not a blocker.
Step 2: Run the migration importer
Rentovation’s migration wizard takes any subset of the three files and runs the import in a deliberate sequence: vehicles first, then customers, then bookings, then photos, so your calendar-critical data lands before slow image fetches, and a photo hiccup can never hold your reservations hostage.
- Column mapping is automatic.The importer auto-detects common headers (including 1Now’s export vocabulary) and shows you the mapping to confirm or adjust before anything is written.
- Photos come along.Image URLs in the export’s trailing columns are fetched and attached to each vehicle automatically.
- You get a receipt. The wizard ends with a verification report of exactly what was imported, so you check the result against your source files instead of trusting a spinner.
Review the imported fleet the same day while the source files are fresh in your head. Confirm vehicle count, spot-check rates, and open two or three vehicles to verify photos.
Step 3: Connect your own payments
Rentovation connects your own Stripe or Square account, so booking revenue settles directly to you, under your name, from day one. If you already ran your own processor with 1Now, this is a reconnect. If not, creating a Stripe or Square account takes minutes, and it is worth doing before the storefront goes live so your first direct booking pays out cleanly.
Step 4: Publish your storefront
Your branded booking site is what replaces the 1Now-hosted page. Set your logo and colors, confirm rates and availability came through, and publish. If you own a custom domain, point it at the new storefront; renters bookmarked on your old URL should land on the new one, not a dead page. Then take one test booking end to end yourself: reserve, sign, pay, and refund it. Ten minutes of pretend-renter now catches what no checklist can.
Step 5: Cut over without losing a booking
The safe pattern is a parallel run, and it is simpler than it sounds:
- Freeze new bookings on the old system once the new storefront is live. Existing reservations keep their dates on 1Now.
- Serve out the old calendar. Bookings made before the switch complete where they were made, unless you imported them and prefer to manage everything in one place.
- Point everything at the new storefront: your website links, social profiles, Google listing if you have one, and your email signature.
- Tell your repeat renters. One short email with the new booking link. Your customer list came over in step 2; this is why.
- Cancel the old subscription when its calendar is empty. Not before.
The two classic migration mistakes are cancelling the old system while it still holds future bookings, and switching the domain before the new site has taken a real test booking. The parallel run makes both impossible.
Bring your fleet over in one sitting
Start a 14-day free trial, run the migration importer with your 1Now exports, and see your own storefront with your own fleet on it before you decide anything. Your cars, your customers, your payments, owned by you.
Start your free trial →Not ready? See how onboarding works step by step, or run your numbers in the fees calculator first.