How to Migrate from Salesforce to Sparkforge

This guide covers a full migration from Salesforce to Sparkforge: data export, data import, rebuilding pipelines and automations, recreating documents and forms, and decommissioning the Salesforce subscription.

1. Prepare for migration

Audit your Salesforce setup

• Catalog leads, contacts, accounts, opportunities, custom fields, and active automation workflows.
• Note record counts and any custom objects so you can size the import.

Define migration objectives

Be explicit about why you're moving — cost, unified comms, easier automation, fewer admins. Use those goals to prioritize what gets rebuilt first.

Back everything up

Export contacts, accounts, leads, and opportunities from Salesforce as CSV. Store the exports somewhere safe before you change anything.

2. Export and import data

Export from Salesforce

• Contacts: Contacts tab > Export. Include name, email, phone, and any custom fields.
• Accounts and Opportunities: Export with deal stages, values, and linked contacts.
• Leads: Export active and closed leads with statuses intact.

Import into Sparkforge

1. Contacts: Contacts > Import Contacts. Map each Salesforce field to a Sparkforge field.
2. Accounts and Opportunities: Recreate the structure and link records to imported contacts.
3. Leads: Import with statuses preserved.

3. Rebuild pipelines, sites, and automations

Pipelines

Create pipelines under Opportunities that mirror your Salesforce stages, then assign migrated opportunities to the matching stages.

Landing pages and ecommerce

• Rebuild landing pages and funnels under Sites > Websites or Funnels.
• Recreate products under Payments > Products.

Automations

Open Automations > Workflows. Recreate triggers (lead conversion, opportunity stage change, form submit) and actions (email, SMS, status updates). Sparkforge has built-in email and SMS, so wire those in instead of routing through a third party.

4. Documents, contracts, and forms

1. Export document and contract templates from Salesforce.
2. Recreate them under Documents in Sparkforge.
3. Enable e-signature and tracking so you can see when contracts are opened, viewed, or signed.
4. Build new forms under Sites > Forms, either from a template or blank.

5. Test before cutover

• Run an opportunity end-to-end through every stage to confirm pipeline behavior.
• Spot-check imported records against the Salesforce export.
• Trigger every workflow with a test contact and confirm emails, SMS, and field updates fire correctly.

6. Train and cut over

Run training sessions for the team and provide written SOPs for the workflows they'll touch every day. Run Salesforce and Sparkforge in parallel for a short window so you can validate live activity before fully switching over.

7. Decommission Salesforce

1. Take a final backup of all Salesforce data.
2. Cancel the Salesforce subscription per their process.
3. Document what worked, what broke, and what you'd do differently next time.

Most teams complete the technical migration in 2–4 weeks. Complex orgs with many custom objects and integrations take longer. If you'd rather not run it yourself, Arcus Foundry offers migration services.