Moving Your Business to Spatiko
Pick the right way to bring your clients, orders, and history into Spatiko — direct migration from HD Photo Hub or Aryeo, or a CSV import from anywhere else.
Last updated
Nobody wants to start over. Whatever you’ve been running your business on, your clients, your past shoots, and the money that changed hands can come across — so your first week in Spatiko shows years of history rather than an empty dashboard.
There are two ways in, and which one you use depends only on where you’re coming from.
Which route is yours
Coming from HD Photo Hub or Aryeo? Use the direct migration. You connect with an API token from your old account and Spatiko pulls the data across itself — far more than a spreadsheet can carry, including shoot appointments, individual payments, and media links.
- Switching from HD Photo Hub — clients, orders, shoot history, payments, and refunds.
- Switching from Aryeo — clients, your product catalog, orders with appointments, payments, and video and tour links.
Coming from anywhere else — another platform, a spreadsheet you’ve kept for years, or an accounting tool — use the CSV imports. If your system can export a file, Spatiko can read it.
- Importing your existing clients — your client list, matched by email so nothing duplicates.
- Importing past orders from a CSV — order history with property, dates, statuses, and totals.
Both CSV imports live in Settings → Data Import, and both can be undone within 48 hours.
Clients first, always
Whichever route you take, import clients before orders. Orders attach to clients by email — so with clients already in place, every order lands on the right record instead of creating a thin duplicate alongside it. The direct migrations enforce this; with CSVs it’s on you to run them in order.
What no migration brings
Your photos. No route copies image files. Videos and 3D tours come across as links where the source has them, but the files themselves stay where they are. Download the galleries you still need to deliver before your old subscription lapses, then upload them into Spatiko for the listings that are still live.
Your booking setup. Services, packages, promo codes, and order forms are quick to build and worth building fresh — see services and pricing. (The Aryeo migration is the one exception: it can bring your product catalog across as a starting point.)
Team logins. Migrations can create team member records so historical shoots attribute correctly, but nobody can sign in until you invite them.
A cutover that doesn’t hurt
- Start small. Import a handful of rows, or run one import type, and check what it produced before committing to the whole history.
- Keep both systems running while you get comfortable. There’s no rush to switch off the old one.
- Do a final pass on cutover day. Both the CSV order import and the direct migrations can be re-run to pick up whatever came in during the transition — as long as your file carries an order ID column.
- On a direct migration, don’t hand-edit imported orders before that final pass. Re-running rebuilds them from the source. The CSV order import works the other way: a row whose order ID is already in Spatiko is skipped and the existing order is left untouched, so edits you’ve made stay put.
- Then rebuild forward: your services and pricing, your order forms, and the integrations you actually use.
If something goes wrong
Nothing here is one-way. CSV imports can be undone within 48 hours, and undo is careful about it: anything you’ve since worked on — an order with media, an invoice, a recorded payment — is kept rather than deleted. Direct migrations don’t duplicate on a re-run, because every imported record remembers where it came from.
New to Spatiko entirely? Start with onboarding and come back here once your account is set up.
Go deeper
- Setting up your Spatiko account — get the account in shape before your first import.
- Client records — what a client record holds once your list is in.
- How orders work — the stages imported orders land in and move through.
- Services and pricing models — rebuild the catalog your new bookings will sell from.
- Connecting your tools — reconnect Stripe, cloud storage, and your calendar after the move.
Frequently asked questions
Will my past orders come across, or only my client list?
Both can. Coming from HD Photo Hub or Aryeo, the direct migration pulls clients and order history together, including shoot appointments, individual payments, and media links. From anywhere else there's a CSV import for clients and a separate one for past orders with the property, dates, statuses, and totals.
Do my photos come across when I switch?
No route copies image files. Videos and 3D tours come across as links where the source has them, but the files themselves stay where they are. Download the galleries you still need to deliver before your old subscription lapses, then upload them into Spatiko for the listings that are still live.
What happens if an import goes wrong partway through?
Nothing here is one-way. CSV imports can be undone within 48 hours, and undo is careful — anything you've since worked on, like an order with media, an invoice, or a recorded payment, is kept rather than deleted. Direct migrations don't duplicate on a re-run, because every imported record remembers where it came from.
Can I keep taking bookings in my old system while I switch?
Yes — keep both running until you're comfortable. On cutover day, both the CSV order import and the direct migrations can be re-run to pick up whatever came in during the transition, as long as your file carries an order ID column. They differ on the re-run, though. A CSV row whose order ID is already in Spatiko is skipped and the existing order is left alone, so your edits survive. A direct migration rebuilds an imported order's line items, sessions, status, and totals from the source — so on that route, do the final pass before you start hand-editing history.