Switching from Salesforce to Lightfield
Lightfield
The short version
Agreed Salesforce records, custom objects, fields, and relationships can migrate into a Lightfield data model that has been set up for them. The logic around those records is assessed separately: formulas, Flows, validation rules, approvals, permissions, and integrations. Importing records doesn't recreate any of them.
Connecting your inbox, calendar, and calls backfills months of conversation history in about an hour. The Salesforce import is a separate, scoped step.
What moves
| Data type | Answer today | What to define first |
|---|---|---|
Accounts | Supported | Source identities and agreed field mappings |
Contacts | Supported | How missing, shared, or duplicate email addresses are handled |
Opportunities | Supported | Account, stages, owners, amounts, and deal contacts, including closed deals, renewals, and expansions if they're in scope |
Custom field values | Supported | The values and their types. Source configuration and business logic don't come with them |
Custom objects | Scoped | Model the objects and relationships in Lightfield, then migrate the agreed records |
Relationships and hierarchies | Scoped | Source identities and explicit mappings, tested for accuracy |
Notes, attachments, and logged emails | Scoped | Standard exports generally don't include full logged-email history, so you may need a separate extraction |
Activity history | Scoped, with limits | The content can be kept. Native timeline, author, and audit-history fidelity isn't established |
Connecting a mailbox and importing from Salesforce are two separate steps. You can keep original Salesforce creation dates in dedicated fields, because Lightfield's own Created At field shows when the record was created in Lightfield. Source stage and property history may need to stay in an archive.
What you rebuild
| Salesforce requirement | Lightfield capability | What to qualify |
|---|---|---|
Flows and process automation | Automations and workflows | You rebuild the agreed process. Automatic Flow conversion and identical behavior aren't established. |
Formula fields | Calculated fields | Check formula compatibility and dependencies. Calculated fields are an Enterprise feature |
Roll-up summaries | Relationship-based calculations | Rebuild and test them. Importing related records doesn't create the calculation |
Validation rules | Assessed for your requirements | Decide which conditions must hold before cutover |
Approval processes | Assessed for your requirements | Decide which approvals must be enforced before cutover |
An exported formula or roll-up value is a snapshot. It doesn't carry the formula, its dependencies, or its recalculation. For each one you have three options:
- Keep the value in a normal field.
- Rebuild the calculation in Lightfield where that's supported.
- Keep the calculation in another system and sync the result under an agreed integration design.
What needs its own assessment
Territory management and multiple Salesforce orgs each get a separate review. For multiple orgs, we look at source identities, schema conflicts, stage mappings, access boundaries, ownership, and which system controls each value.
How a migration is planned
We estimate a migration after reviewing your data model, volume, historical content, integrations, and testing needs. The plan separates source preparation, model setup, the first import, historical content, testing, corrections, integrations, and the final cutover. Managed migration is available on request, with scope and terms agreed per customer. Our average migration is 6 days.
Check these before you plan a cutover
- Records, custom objects, fields, and relationships
- Pipelines and permissions
- Formulas, Flows, validation rules, and approvals
- Integrations and reports
- Any historical audit requirements
Who this guide fits
This guide is for teams moving their data and rebuilding selected processes in Lightfield. It doesn't promise that Salesforce Flows, validation rules, and approval processes will behave the same way afterward. If you need exact Salesforce behavior, test those dependencies first. A team with heavy Salesforce-specific governance can reasonably stay on Salesforce until it has confirmed Lightfield can meet those requirements.
FAQ
What can move from Salesforce to Lightfield?
Agreed accounts, contacts, opportunities, custom field values, custom objects, and relationships can migrate into a Lightfield data model set up for them. Notes, attachments, logged emails, and activity history are scoped separately.
Do Salesforce Flows move over?
No. Importing records doesn't recreate Flows. You rebuild the agreed process with Automations and workflows.
What happens to formula and roll-up fields? An exported value is a snapshot of the result, not the rule behind it. You can keep the value, rebuild the calculation where supported, or keep it in another system and sync the result.
Do custom objects migrate?
Yes, as scoped work. You model the objects and relationships in Lightfield, then migrate the agreed records. Lightfield doesn't copy a Salesforce schema automatically.
How long does a migration take?
It depends on scope. We estimate after reviewing your data model, volume, historical content, integrations, and testing needs. The plan separates the first import, testing, corrections, and final cutover. Our average migration is 6 days. Most decently large Salesforce migrations can occur in less than 30 days. The bottleneck is time spent in human review of process and decisions.
Does Lightfield keep original Salesforce creation dates?
You can keep them in dedicated fields. The system Created At field shows when the record was created in Lightfield.
Does Lightfield support territory management or multiple Salesforce orgs?
Both need their own review. Before planning, we look at source identities, schema conflicts, stage mappings, access boundaries, ownership, and which system controls each value.
Can Lightfield run alongside Salesforce during the move?
Yes. Running in parallel is supported through scoped deployments, using one-way or two-way sync. You scope the overlap before it starts.
Next step
Book a demo to review your Salesforce data model and scope the migration.
