Migration Center
Switch to Spark ERP.
Moving off a legacy system is the biggest fear in any ERP decision. Here's exactly how it works, what's automated today, and what isn't yet.
1. Assess
We review your current system, data volumes and integrations with you, and scope which applications and modules you need on day one vs. later.
2. Map
Your fields map to Spark ERP entities using the Entity Designer’s schema — the same tool your team can use later to extend the model yourselves.
3. Migrate
Data moves in via CSV/Excel import templates or a real connector (see Integrations), in a staging tenant first, never directly into production.
4. Validate
Row counts, reference integrity and a sample reconciliation against your source system are checked before anything is promoted.
5. Go Live
Cutover happens on a scheduled date you control, with the old system kept read-only as a fallback for an agreed period.
Coming from...
Honestly labeled — a "manual" path means a documented CSV/Excel import today, not an automated connector we don't have yet.
SAP (ECC / S/4HANA)
Manual (CSV/Excel) todayCSV/Excel export from SAP, mapped to Spark ERP entities via Data Import. No packaged SAP connector today.
Oracle (E-Business Suite / Fusion)
Manual (CSV/Excel) todayCSV/Excel export, mapped via Data Import. No packaged Oracle connector today.
Microsoft Dynamics 365
Manual (CSV/Excel) todayExport to CSV/Excel or via Dynamics’ own OData export, then Data Import.
Odoo
Manual (CSV/Excel) todayOdoo’s built-in CSV export maps cleanly to Spark ERP’s entity structure for most modules.
Zoho (Books / CRM / People)
Real connectorA real Zoho integration connector exists under Integrations for ongoing sync; historical data still moves via CSV import.
Spreadsheets (Excel / Google Sheets)
Documented todayThe most common starting point — direct CSV/Excel import with a documented template per entity.
Custom / in-house ERP
Manual (CSV/Excel) todayExport whatever your system can produce as CSV/Excel or via its own API; we map it to Spark ERP entities with you.
Migration documentation & templates
Every entity has a documented CSV/Excel import template in Developer Docs, built with the same Data Import tooling your team uses after go-live. Staging-tenant migrations never touch production data until validation passes.
Talk to us about your migration.
Every migration is scoped with your actual data before we commit to a timeline — no generic promises.