Running Lightfield alongside Salesforce

The short version

You can agree to a phased rollout where Lightfield runs next to your existing CRM. Before the overlap starts, we define which records and fields sync, which system owns each field, how conflicts are handled, and what has to be true before cutover. Scoped pilots can use one-way or two-way Salesforce sync. Ongoing two-way sync that we manage is Enterprise or custom integration scope, unless your agreement says otherwise.

Define the overlap by conditions

We don't give a fixed number of days for an overlap. A parallel run is defined by its operating conditions and by what counts as done. Agree these before it starts:

• The objects and fields in scope
• Whether data moves one way or both ways
• Which system controls each field
• How records are matched and conflicts are handled
• Ownership and permissions
• How failures are monitored and reconciled
• What counts as ready for cutover, and the final delta work

Plan for an initial export and a final delta

Connecting a mailbox doesn't keep every change in the old CRM current. A common pattern is an initial export, then a final delta close to cutover. The final delta is whatever changed in the old CRM after the initial export, loaded just before you switch.

Keep a calculation where it lives

If another system depends on a calculation, one option is to leave it where it is and sync the result under an agreed integration design. Importing related records doesn't recreate a Salesforce formula or roll-up in Lightfield.

What a record export covers

You can export your CRM records from Lightfield. A broad export can cover accounts, contacts, opportunities, custom objects, tasks, notes, and meetings, as CSV, Excel, or JSON. It isn't a complete, restorable backup of the workspace. Email history, attachments, transcripts and recordings, archived or deleted records, and workspace settings need separate handling, so list any you need in your exit plan.

If you plan to leave, agree to the full export scope and finish it before access ends, including any historical content or attachments you need.

Who this guide fits

This guide is for teams that want Lightfield alongside their current CRM before a cutover. If you need a fixed overlap length in days, this guide doesn't give one, because the right length depends on your scope.

FAQ

Can Lightfield and Salesforce run together? Yes. Running in parallel is supported through scoped deployments.

Is the sync one-way or two-way? Scoped pilots can use either. If a deployment needs two-way sync, that's agreed in its scope.

How long should the overlap last? We describe operating conditions and what counts as done, not a number of days. The list above is where planning starts.

Which system owns each field? You decide before the overlap starts. Each field has one controlling system, and the plan says how conflicts are handled.

Do Salesforce edits show up in Lightfield automatically? No, not unless a sync is scoped. Edits made in the old CRM don't appear in Lightfield on their own.

What is a final delta? It's the set of changes made in the old CRM after the initial export, loaded close to cutover.

Can I export my records if I leave Lightfield? Yes. You can export your CRM records. Agree the full export scope and finish it before access ends.

Does a record export cover everything? No. It isn't a complete, restorable backup. Email history, attachments, transcripts and recordings, archived or deleted records, and workspace settings need separate handling.

Next step

Book a demo to scope a parallel run for your Salesforce setup.