Aeion CRM — Salesforce Migration Guide
Leaving Salesforce is the most common Aeion CRM adoption scenario. Singularity's Salesforce connector does the data pull — a one-way, on-demand read import of Accounts, Contacts, Leads, Opportunities, Cases, Tasks, Campaigns, and Products via Salesforce's REST/SOQL API. You field-map each object into your target Aeion collections during setup (typically Accounts → companies, Contacts → contacts, Opportunities → deals); workflow automation gets rebuilt in Blueprint. There's no automatic reverse-sync back to Salesforce, so plan the cutover as a one-way trip. Plan 6-12 weeks depending on Salesforce feature usage.
The Salesforce Migration Decision
Teams typically leave Salesforce for one or more of:
What the Connector Actually Imports
Singularity's Salesforce connector supports a fixed set of standard objects, pulled read-only via SOQL. You choose the target Aeion collection for each object during import setup — it's a configured field mapping, not an automatic opinionated one.
Migration Playbook — One-Way Import, Staged Cutover
Be clear about the mechanics up front: Singularity's Salesforce connector is a one-way, on-demand read import. It doesn't run continuously in the background, and there's no reverse-sync back to Salesforce. "Dual-run" here means re-triggering the import periodically to pull in what changed since the last run (using the connector's modifiedSince filter), not an automatic continuous sync — you (or your automation) decide when to re-pull.
Field Mapping Patterns
Salesforce's field naming + types map to Aeion's collection model.
Common Migration Gotchas
- Custom Apex triggers — these have no automated migration. Inventory each trigger + rewrite as Aeion service callbacks or Blueprint workflows. Most teams have 5-20 Apex triggers; budget 1 week / 5 triggers for the rewrite.
FAQ
6-12 weeks for typical mid-market deployments (20-50 reps + moderate customization). 4-6 weeks for simpler teams (10 reps, minimal custom). 4-6 months for enterprise migrations with heavy Apex + Service Cloud + Marketing Cloud.
Migration consulting is available from the Aeion team on top of the flat $49/mo price. Most migrations don't need outside consultants — the connector + admin UI cover the standard objects. For complex Apex rewrites or anything on the "Not supported" list (Quotes, custom objects, files), budget $25-100K external dev cost (1-3 month engagement).
Yes — split migration is supported. Sales Cloud → Aeion CRM; keep Service Cloud + Marketing Cloud on Salesforce; re-run the connector's one-way read pull periodically for any linked data you still need visibility into.
Before cutover, Salesforce stays primary and Aeion holds a read-only snapshot you refresh as needed — rolling back here just means continuing to use Salesforce. After a team fully cuts over, there's no automated reverse-sync: rolling back means manually re-entering or CSV-importing whatever changed in Aeion back into Salesforce. Plan cutover per-team specifically so a rollback, if needed, is scoped to one team's data, not everyone's.
They'll be productive on Aeion within 2-4 weeks. Aeion's admin UI + collection model is simpler than Salesforce's config; the Salesforce knowledge of business processes transfers; only the platform-specific knowledge (Apex, SOQL, Lightning) becomes obsolete.
Salesforce contracts are annual + auto-renew. Plan to start migration 4-6 months before contract renewal. Most teams complete cutover before renewal + don't renew.
Low, if you re-run the import before each team's cutover. The connector gives you a fresh read-only snapshot on demand — take one right before a team's cutover so nothing recent is missed. Aegis backups protect ongoing Aeion data. Salesforce remains source-of-truth until a team cuts over; even after cutover, Salesforce export stays available for read-only reference.