What if the import goes wrong?

It tells you first. Your file is read in your own browser and checked before a single byte is uploaded, and then a practice run resolves every row against your real data and reports what would happen without saving anything. You only press the real button once you have seen the numbers.

Can I bring it in twice?

Yes. Records are matched on their natural key (SKU for products, email for customers, order number for orders) so running the same file again updates rather than duplicates. Fix something in the spreadsheet and re-drop it.

For most businesses there is nothing to do. It is a file and a button. If your data is genuinely awkward, email migrate@sparx.works and we will do the move with you.

← Every platform we move you from

Built for a company with a Salesforce administrator

Accounts, contacts, leads, opportunities and cases: from the list-view exports you already know how to make.

Start moving →What it costs

One export per object. Half a day for a CRM with years in it.

accounts.csv

read locally

This is a Salesforce accounts export

We can tell from the columns and the file name.

Accounts

128 of 129 ready

128 accounts ready: 1 row will be skipped.

Must fix

Row 84: this record has no name.

Nothing has been saved yet.

You are paying for capability you cannot reach.

1

Nothing changes without somebody who knows the system

A field, a rule, a report. Either you learn a platform for a living or you pay somebody who has.

2

The licenses are the small part

The consultant, the admin, the integrations, the annual review. The seat price was never the number that mattered.

3

Most of it is switched off

You use accounts, contacts, opportunities and maybe cases. You are paying for a platform sized for a sales floor of two hundred.

What comes across

Everything in this list is something an importer we maintain actually reads out of your Salesforce export. It is generated from that importer, so it cannot promise you something we do not do.

CustomersCompaniesDealsTickets

The files you need from Salesforce

Accounts

Accounts → pick a list view → Printable View or Export

accounts.csv

Contacts

Contacts → pick a list view → Export

contacts.csv

Leads

Leads → pick a list view → Export

leads.csv

Opportunities

Opportunities → pick a list view → Export

opportunities.csv

Cases

Cases → pick a list view → Export

cases.csv

The parts you use, without the operating model.

sparx does accounts, contacts, deals with real pipelines, and support tickets, and joins them to the orders, invoices and email, which Salesforce charges extra to approximate. The person who runs the sales process configures the sales process.

What that changes

Leads and contacts arrive as one kind of record with a lifecycle, which is what they always were.
Opportunities keep their stage, amount and close date, and won/lost is read correctly.
Cases become support tickets attached to the same customer.
No admin, no consultant, no annual review.

What does not come across

Every migration leaves something behind. Here is ours, so it is not a surprise halfway through.

Custom objects, Apex, flows and validation rules do not come across.
Reports and dashboards are rebuilt: the ones you actually look at, usually in an afternoon.
Chatter and activity history stay behind.

Before you start

Still curious? Read the platform docs, browse the API spec, or book a 20-min architecture call. We don't do high-pressure demos.

No. Everything happens on a copy. You export a file, and your Salesforce account carries on exactly as it is. Plenty of people run both for a few weeks before switching their domain over.

Bring it over

Export the file Salesforce already makes for you, drop it in, and look at what would happen before anything is saved. One export per object. Half a day for a CRM with years in it.

Get started →Ask us to do it