Clients, priced quotes, the drawing that goes with them, and next month's calendar — brought over by CSV, by phone contact list, or by dropping a screenshot of the old system and letting the app read it. Every import is logged, and every import can be undone.
Ask an owner why they have not switched and you get the same two answers. "I have eleven years of jobs in there." And: "Somebody would have to retype six hundred clients and every open quote, and that somebody is me, at night, after the shop closes."
Both are fair. So the importers were built for the mess a real migration actually is — a half-usable CSV export, a price list nobody has audited since 2019, forty open quotes you cannot afford to lose, and a calendar that already has installs booked for next month.
1. Materials and colors first. Everything priced downstream points at a material. Bring the catalog in before the quotes and each imported line finds a real slab to attach to; bring it in after and you spend the evening relinking line items by hand.
2. Then set your price list. Your price book is built in the app, per material and per service, so it is worth an hour of attention rather than a paste from a spreadsheet nobody has audited. It also becomes the yardstick: from that point on, every import compares the old price against yours and flags the gaps instead of quietly importing a rate you stopped charging two years ago.
3. Then clients and accounts. CSV for the bulk of the list, phone contacts for the ones that only ever lived in somebody's cell, QuickBooks Online for the ones you already invoice. Builders and GCs come in as accounts, so the individual homeowners underneath them stay attached to the right company.
4. Then open jobs and quotes. Now that materials, prices and clients exist, an imported quote lands complete: linked to the right client, priced against your book, with its drawing on the canvas. This is also where you stop and decide how much history is worth carrying. Most shops bring what is still open and leave the closed years in the old system until the subscription lapses.
5. Calendar last. Screenshot next month's schedule, review what the app read — type, date, crew — and commit. Do it last so an install can point at a job that already exists.
Old systems are generous with data entry and stingy with exports. If yours will not hand over a usable file, open the quote on screen, capture it, and drop the image into Stone Project. The app reads it the way an estimator would: who the client is, which builder it came through, who sold it, what each line cost, and what the countertop actually looks like.
Then it shows you everything before writing a single record. Client details next to any existing client with a similar name, so you can link instead of duplicating. The line items with their original totals, each one compared against your price list. And the drawing, rebuilt piece by piece on the canvas — dimensions, cutouts, edge profile — so you can see immediately whether the read was right.
Drop twenty at once if you like. They queue up and get reviewed one at a time, and a bad image gets skipped rather than killing the batch. Only when you press Create in system does anything exist: client, quote, project and drawing, all linked.
What migration looks like when the tooling expects a mess
No. CSV is the fastest way to move a long client or material list, and we map your columns for you. But if the export is locked down, comes out mangled, or you simply do not want to fight with it, the screenshot importer reads a quote screen straight off your monitor instead.
That is a supported path, not a workaround. Drop one image or twenty (JPG, PNG, WEBP or PDF) and the app reads each quote screen: client, builder or account, salesperson, every priced line item, and the drawing. You review each one and press Create in system. Nothing is written until you do.
The drawing comes across. The importer rebuilds the pieces on the drawing canvas with their dimensions, cutouts and edge profile, and you see them before you commit. It is a real, editable drawing, not a picture of one. Complicated layouts are worth a look on the review screen before you press create.
That depends on what you bring. A client list or material catalog is a CSV and a column mapping: minutes. Screenshot imports run one quote at a time, so budget about a minute each including your review. Most shops only carry open jobs across and leave closed history in the old system until the subscription runs out.
Yes. Import history lists every batch you have run, with how many records it created and how many it updated, and each one has an Undo. Undoing removes what that batch created and restores what it changed. If someone has already built on top of an imported record, the app blocks the undo and tells you exactly which records are involved instead of silently deleting their work.
We help. Book a demo, bring a sample export or a couple of screenshots of your current quotes, and we will map the fields with you on the call and run the first import together.
Systemize, CounterGo and a separate CRM against one mobile-native app. Side-by-side on price, quoting, mobile and remnants.
Where your imported clients and jobs land: a visual kanban from Lead to Done, with role-based permissions and a client portal.
The canvas your imported drawings arrive on — pieces, edges, cutouts and splashes, priced as you draw.
Start a free trial and import a single job, or book a 20-minute demo and we will do the first one with you. No credit card required.