Switching from Aryeo

Leaving Aryeo shouldn’t mean rebuilding your business in an empty account. Spatiko’s Aryeo integration is a one-time migration: you connect with an API token, then run three imports — clients, catalog, orders and payments — and day one in Spatiko already looks like the business you’ve been running for years.

What comes over

Aryeo Migration Connected

Import your clients, catalog, and orders from Aryeo.

Import Data

Team members

Match Aryeo team members to Spatiko team members so imported shoots are assigned correctly. Map first — orders use this (re-import to apply).

Map

1. Clients

Import your client list with names, emails, phone numbers, and notes.

Jul 22, 2026, 9:12 AM — 316 imported, 4 skipped

Re-import

2. Catalog

Import Aryeo products as Spatiko services, including variations and prices. Coupons and order forms are not imported — recreate those manually.

Jul 22, 2026, 9:19 AM — 18 imported, 2 skipped

Re-import

3. Orders & Payments

Import orders with appointments, payments, videos, and 3D-tour links. Photos are not imported yet.

Jul 22, 2026, 10:04 AM — 642 imported, 12 updated, 2 failed (2 errors)

Re-import

Disconnect

• Clients — name, email, phone number (normalized to international format), and the brokerage or office name from the Aryeo customer record. Internal notes come across as-is, and if a customer had a credit balance in Aryeo, it’s noted on the client so you don’t lose track of money you owe them.
• Catalog — Aryeo products become Spatiko services. A product with one variation becomes a flat-priced service; a product with several becomes one service with named variations, each keeping its own price and duration. Aryeo add-ons stay add-ons, and inactive products come over inactive.
• Orders — one Spatiko order per Aryeo order, with the property address and square footage, every line item, order totals, discounts, tips, and internal notes. Canceled line items come over marked voided rather than being dropped, so the history stays complete.
• Appointments — each appointment becomes a shoot session on the order, with its start and end time, the photographer assigned to it, and the specific line items that were booked for that visit. Canceled and draft appointments are left behind.
• Travel fees — Aryeo fee lines named like travel (travel, trip charge, trip fee, mileage, fuel or gas surcharge) are recognized and land in the order’s travel fee field, where your reports expect them, instead of sitting among the services.
• Payments — every completed payment, with its method translated (Stripe becomes a card payment; cash and check keep their names; PayPal, Venmo, Square, account credit and anything else land as “external”). Tips are pulled out and recorded as the order’s tip rather than being buried inside the payment amount.
• Videos, tours, floor plans, and property websites — YouTube and Vimeo videos come over as embedded videos on the order; Matterport and other interactive tours, floor plan images, and the Aryeo property website come over as content links, the same as anything you’d embed by hand.

Order statuses are translated, not guessed at: canceled orders arrive as Cancelled, fulfilled or delivered ones as Completed, orders whose first shoot is still in the future land in Planning, and everything else in Production — the same order lifecycle your new bookings follow.

Dates are preserved throughout. Each order keeps its original creation date and picks up an “Imported from Aryeo” entry in its activity log, orders show Aryeo as their source, and every client’s start date is rolled back to their earliest imported order. Your reports read like your real history instead of like everything happened on migration day. And if a listing in Aryeo never had an order attached to it, Spatiko still creates an order from the listing so the property and its media aren’t lost.

What doesn’t come over

• Photos. Image files stay in Aryeo — videos and tours come across as links, not copied files. Download the galleries you still need from Aryeo before your subscription lapses, then upload them into Spatiko for the listings you’re still delivering.
• Coupons and order forms. Rebuild your promo codes and order forms in Spatiko. It’s quick, and it’s a good moment to drop the ones you stopped using.
• Historical payouts. Imported shoots show who shot them, but per-photographer pay doesn’t come across, so imported orders don’t add amounts to payout reports. Settle the pre-migration period from your existing records.
• Team logins. You can bring Aryeo team members over as records (step 2), but they can’t sign in until you invite them.
• Draft orders. Anything still a draft in Aryeo is skipped — finish or discard drafts there before your final import.

Step 1: Connect with an API token

There’s no OAuth popup for this one. In Aryeo, generate a personal access token from your group’s Settings → Developers. Then in Spatiko, open Settings → Integrations, find Aryeo under Migration, and paste it in.

The token is checked against Aryeo before it’s saved, so a typo or an expired token is rejected right away instead of failing halfway through an import. It’s stored securely, like every other integration credential, and you can disconnect from the same dialog once you’re done migrating.

Step 2: Map your team

Open the integration and click Map next to Team members. This matches each active Aryeo team member to a Spatiko team member so imported shoots land on the right photographer instead of arriving unassigned.

If someone isn’t on your Spatiko team yet, import them straight from the mapping dialog. That creates an inactive team member record with no login — enough to attribute historical shoots — and they won’t appear for new bookings until you invite them and they accept.

Do this before importing orders. The mapping is applied while orders are being imported, so anyone you map afterwards needs a re-import to take effect. Anyone left unmapped simply leaves those shoots unassigned, which you can fix later.

Step 3: Import your clients

Click Import next to Clients. For each Aryeo customer, Spatiko either creates a client record or — if a client with the same email is already in your account, say from an earlier CSV import — links to that record and fills in the blanks instead of duplicating it. Details you already have are never overwritten. Customers with neither a name nor an email are skipped.

Run this first: the Orders & Payments import stays locked until clients are in, so that every order attaches to the right client.

Step 4: Import your catalog

Aryeo products become Spatiko services, with their variations, prices, and durations intact. This import is independent of the other two — imported orders carry their own historical line items and don’t get relinked to these services — so nothing breaks if you run it later or skip it entirely and build your catalog by hand.

Four things are worth reviewing right after it finishes:

• Products with no variations at all arrive as inactive $0 services. Set a price and switch on the ones you still sell; leave the rest inactive. A product that does have a variation but no price on it comes across active at $0, so it’s worth scanning your new catalog for zeros either way.
• Durations default to 60 minutes wherever Aryeo didn’t have one. Duration drives scheduling and travel time, so correct these before you start taking bookings.
• Service type (photography, aerial, video, virtual tour, floor plans, add-on) is inferred from the product and category names. Skim the list and fix any that guessed wrong — type is how your catalog is grouped.
• Variation names become what clients see on your booking form. “Option 2” reads fine in an internal system and badly on a public form.

Coupons and order forms aren’t part of this import; recreate those in Spatiko.

Step 5: Import orders and payments

This unlocks once clients are imported. Spatiko walks your Aryeo orders first, then your listings, building everything described above — orders, shoot sessions, payments, and media links.

A few things to know before you run it:

• If your Aryeo account doesn’t return itemized payments, Spatiko records a single reconciling payment per paid order so the paid and outstanding totals still match. It shows up as an external payment with a note explaining where it came from.
• Orders billed in another currency are imported with their amounts unchanged and flagged in the import summary. Worth a look if you’ve ever invoiced across a border.
• Videos that were hidden in Aryeo come over but aren’t marked deliverable, so they won’t appear in client-facing delivery galleries until you say so.
• If you also run HubSpot sync, imported orders don’t trigger deal sync — the migration won’t push years of historical deals into your CRM.

Re-running an import

Every imported record is keyed to its Aryeo ID, so re-running an import updates what’s there instead of creating duplicates. Three common reasons to run it again:

• You mapped more team members after the first pass and want their shoots assigned.
• You kept booking in Aryeo during the switch, so there are new orders to pull.
• Payments came in against orders you’d already imported.

One caution: re-importing rebuilds an imported order’s line items, sessions, status, and totals from Aryeo, which is treated as the source of truth. If you’ve hand-edited an imported order in Spatiko, a re-import overwrites those parts — so finish your final import before you start touching history. Payments that already came across aren’t duplicated.

How long it takes, and what happens on errors

Imports run in the background. Close the dialog and get on with your day; progress picks up where it left off next time you open it. Large accounts take several minutes. Only one import runs at a time, and if one ever appears stuck it clears itself after about 30 minutes so you can start again.

Records that fail don’t stop the rest. When the import finishes you get a summary — imported, updated, skipped, failed — plus the individual error messages, so you know exactly what needs a manual touch-up rather than wondering whether everything made it.

A clean cutover, in order

1. Connect Aryeo and map your team.
2. Import clients, then catalog, then orders — in that order.
3. Spot-check a handful of imported orders: property address, shoot sessions and who’s assigned, totals, payments, and the video and tour links.
4. Tidy the catalog — prices, durations, service types, variation names — before you point any order form at Spatiko.
5. Keep taking bookings wherever you like until you’re ready, then run one final import on cutover day, before you edit any imported order.
6. Pull your photos out of Aryeo before the account lapses. Media is the one thing the migration can’t bring with it.

Coming from somewhere else? There’s the same kind of migration for HD Photo Hub, and the CSV client import works with any system that can export a spreadsheet.

Go deeper

• Moving your business to Spatiko — the full picture of migration routes and a cutover that doesn’t hurt.
• Services and pricing models — tidy the imported catalog before you take a booking on it.
• Packages — bundle those imported services into the offers you actually sell.
• Getting paid — set up how new bookings get paid, now that the history is in.
• Uploading and processing media — bring your photos over yourself, since the migration can’t.