Migration

Moving your studio in

You have years of clients, a price list you have tuned over time, and a pile of past jobs. Here is what you can bring across yourself, what you cannot, and where a person sits down and does it with you.

Start with the part most software pages skip

There is no button that reaches into your current software and pulls your business out of it. Every product guards its own exit, and none of them gives us an interface to plug into, so anyone promising a one click migration is describing an ambition rather than a feature.

What exists instead is a CSV import you drive yourself for the three things that matter most, and a person for everything else. That is less impressive on a slide, and in practice it is faster, because the slow part of a migration was never the upload. It is deciding what is worth carrying over.

Three things you can move yourself

They live in the app under Settings, then Import. Each one has its own template, its own preview, and its own key for matching records you have already brought in.

Your client book

Email is the one required column, and it is also what we match on, so uploading a corrected file updates the same clients instead of creating a second copy of everybody. Name and company are optional. Matching ignores capitalisation.

Your price list

Services, each with a name and a plain decimal price. The name is the key. There is an optional unit, which can be per image, per order, per video, or per hour, and it defaults to per order when you leave it blank.

Your past jobs

Orders, keyed on whatever job reference your old system used. Each row links to a client by email and, optionally, to a service by name, so import those two first. A row can also carry a status, a quantity, a price, and a shoot date.

How the import actually works

Two things worth knowing before you upload

Each file can be up to 10 MB and 50,000 rows. And importing records does not start a workflow or send anything to your clients, so bringing four years of history in does not send four years of follow ups back out.

What the CSV import does not carry

This is the honest list. If something on it matters to you, raise it before you move rather than after.

The parts we do with you

For anything the import does not cover, and for exports that do not look like anything we have seen before, the answer here is a person rather than a feature. Send us the files you can get out of your current product. We read the actual columns, tell you plainly what maps and what does not, prepare the files, and run the preview with you before a single record is written.

We deliberately do not ship built in presets for other products' export formats. We went looking, and none of them publish their export column names, so a preset built on a guess would quietly put your clients' phone numbers in the wrong field. Your real file beats our assumption every time, which is exactly why this step has a human in it.

Questions people actually ask

Can you connect to my current software and pull the data across?

No. There is no live connection, no logging in to your old product on your behalf, and no scheduled sync. Migration here is file based. You export from your side, we agree how the columns map, and you upload.

What happens if I upload the same file twice?

Nothing bad. Clients match on email, services match on name, and jobs match on your own job reference, so a second upload updates the records that already exist rather than duplicating them. That is why fixing a few rows and re-uploading the whole file is the intended way to work.

Will my clients get emailed when I import?

No. An import writes records and stops there. Workflows and client emails are triggered by what you do in the app afterwards, never by the import itself.

Migration help

Send us your export and we will tell you what moves

No commitment and no sales call needed. We look at the real columns and give you a straight answer about what can come across and what cannot.