Running Lightfield alongside Salesforce: plan a parallel run and a cutoff

Lightfield

The short version

Yes, you can run Lightfield and Salesforce side by side, for example when some processes aren't ready to move yet. Lightfield is the CRM designed for trusted agent work, and a parallel run keeps both systems usable while you decide what syncs and which system owns each value. We set the length of the overlap by the acceptance criteria you agree on, not by a fixed number of days.

What a parallel run covers

A pilot can use one-way or two-way sync with Salesforce, and we define the requirements for two-way sync with you for each deployment. Edits made in Salesforce don't appear in Lightfield unless a sync is set up for them. Connecting your mailbox keeps new email current, but it doesn't mirror changes in your old CRM. A common pattern is an initial export, then a final delta close to cutover.

Decide these before the overlap 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 how conflicts are handled
  • Ownership and permissions
  • How failures are monitored and reconciled
  • What counts as ready for cutover, and the final delta work

How long should the overlap last?

It lasts until you meet the acceptance criteria you set. Typical criteria are reconciled record counts by object, sampled fields that match, tested associations, and a completed final delta. Define the criteria first and end the overlap when they pass.

Working back from a fixed date

If the move is tied to a date, such as a Salesforce renewal, set the cutover date first. Then set the date of the final delta and the acceptance checks that must pass before it. Your Salesforce contract terms are between you and Salesforce, so confirm them with your account team. This guide covers the technical plan.

If finance or another team still reads from Salesforce

List every team that reads from or writes to Salesforce, including finance. For each value they use, choose one of three options:

  1. Keep the source value in a standard field.
  2. Rebuild the calculation in Lightfield where it's supported.
  3. Keep the calculation in another system and sync its result under an agreed integration design.

A team with heavy Salesforce-specific governance can stay on Salesforce until it has confirmed Lightfield meets its requirements.

Before you switch off Salesforce

  • Reconcile record counts by object and scope.
  • Review skipped or missing records and the reason for each.
  • Sample fields, currency amounts, dates, stages, and owners.
  • Test associations between accounts, contacts, deals, and custom objects.
  • Confirm the actual contacts on each deal, not every contact at the account.
  • Check historical emails, notes, and transcripts against source examples.
  • Decide what stays in an archive.
  • Test rebuilt formulas, workflows, permissions, and review requirements.
  • If the systems will coexist, test integration conflicts and failure recovery.
  • Complete the final delta pass and get sign-off.
  • Keep agreed backups and source access until sign-off is complete.

If you ever leave Lightfield

You can export CRM records as CSV, Excel, or JSON, and the agent can export accounts, contacts, opportunities, meetings, tasks, notes, and custom object records on request. A record export 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. If you plan to leave, agree the full export scope and finish it before access ends.

FAQ

Can Salesforce and Lightfield run together?

Yes. We define the records and fields in scope, which system owns each field, how conflicts are handled, and the criteria for cutover.

Is the sync one-way or two-way?

Either can be set up for a pilot. We define two-way requirements with you for each deployment.

Can we agree on an overlap period without a number?

Yes. Describe the operating conditions and acceptance criteria instead of a number of days.

Do edits made in Salesforce appear in Lightfield automatically?

No, unless a sync is set up for them. A common pattern is an initial export plus a final delta near cutover.

How do we leave Salesforce mid-contract?

Work back from your cutover date and the acceptance checks that must pass first. Your Salesforce agreement is separate, so check its terms with Salesforce.

What if finance still runs reports from Salesforce?

List the values finance uses. Then keep each as a snapshot, rebuild the calculation in Lightfield where it's supported, or keep it in another system and sync the result.

What stays in an archive?

Source stage and property change history may need to stay in an archive, because it generally isn't replayed natively. Keep agreed backups and source access until sign-off.

Can we export our records from Lightfield?

Yes. A record export isn't a complete workspace backup, so agree the full export scope for email history, attachments, transcripts, and settings if you need them.

Next step

Book a demo and bring your Salesforce object list, plus the Flows, validation rules, and approvals you rely on.