Insight 3.0 Salesforce Classic and Lightning

Your till and your CRM,
telling the same story.

Insight keeps Lightspeed R synchronised with Salesforce in near real time. Customers move both ways. Sales, products, employees, shops and registers arrive in Salesforce on their own. No exports, no overnight batch, no reconciliation spreadsheet.

See every field mapping

Polls Lightspeed as often as every five minutes. Salesforce edits queue instantly.

Point of sale
Lightspeed R
poll 5 min
CRM
Salesforce
queue instant
0
records in flight
5 min
Fastest Lightspeed polling interval
6
Lightspeed objects pulled into Salesforce
55+
Documented field level mappings
2 way
Customer sync, Lightspeed and Salesforce
How it works

Two directions,
two different speeds.

Insight runs in two modes depending on which way the data is moving. Both are near real time, and neither one needs a person to press a button.

Polled, as often as every five minutes

Insight asks Lightspeed for anything that changed since it last looked. You choose the interval, down to five minutes.

Interval you control Customers, sales, products Employees, shops, registers

Queued the moment you hit save

Any Account or Contact update in Salesforce is queued immediately and sent as fast as Lightspeed's API will accept it.

Queued on save Accounts and Contacts API paced delivery
Lightspeed
Salesforce
1

Insight polls Lightspeed on your interval, as often as every five minutes.

2

Changed customers, sales, quotes, items, employees, registers and shops are collected.

3

Records are compared against Salesforce so duplicates are not created.

4

Sales land as a Closed Won Opportunity and an Activated Order, line items included.

1

An Account or Contact is updated in Salesforce and saved.

2

That record is queued immediately, no waiting for the next poll.

3

Insight sends it as quickly as Lightspeed's API will accept changes.

4

Bulk updates are paced deliberately, so a mass edit does not overrun the queue.

What syncs

Six objects. One click to see every field.

These are the real mappings from the Insight product overview, not a marketing summary. Open any card to read the field level detail, including the Person Account variants.

Field mapping explorer

Search the whole mapping table.

Type a Lightspeed field, a Salesforce label, or an API name. If your team has ever argued about where the fax number ends up, this settles it.

Object Lightspeed field Sync Salesforce field
0 of 0 mappings shown
⇆ Bidirectional → Lightspeed to Salesforce × Does not sync

Insight cannot sync Lightspeed R custom fields. Everything else above is standard.

Conflicts and duplicates

When both systems are sure they are right.

Two way sync only works if disagreements are handled honestly. Insight flags them instead of guessing, and compares records before writing so you do not end up with two of the same customer.

Duplicate prevention

Account and contact details are compared before creation, so the same customer does not appear twice.

Flagged for review

When the same field is edited differently in each system, the record is held for a human decision.

Pick once, both update

Choose the correct value and Insight writes it to both platforms. The conflict closes.

Sync only what you want

Configuration decides what is in scope. Anything you leave out simply does not move.

Insight › Conflict review

Mobile phone was changed in both systems since the last sync. Pick the value that should win.

See it running

Two minutes beats two paragraphs.

Short walkthroughs of Insight moving live data between Lightspeed and Salesforce.

Cost of doing nothing

What manual re-keying actually costs you.

Move the sliders to match your shop. This is your own arithmetic, not ours, so bring it to the call and we will pressure test it together.

250

New customers, address edits, sales that need to reach Salesforce.

2.0 min

Look it up, retype it, check it, fix the typo.

$32

Salary plus overhead for whoever currently does the re-keying.

6%

Duplicates, stale addresses, sales attributed to the wrong shop.

Your first year

$0
net position after year one
Hours spent re-keying, per year0
Labour cost of manual entry$0
Rework on records that go wrong$0
Insight, year one, all in$10,000
Payback period0 months

Year one uses the published $1,500 installation and $8,500 annual subscription. Rework is costed at three times a single manual entry, since somebody has to find the problem before fixing it.

Pricing

Published, and that is the whole list.

One installation fee, one annual subscription. No per seat pricing, no per record metering.

Installation

$1,500one time

For a basic configuration. Advanced data mapping may incur additional fees.

  • Package install into your Salesforce org
  • Lightspeed R connection and polling setup
  • Standard field mapping, Person Accounts included
  • Sync scope configured to your rules
Ongoing

Annual subscription

$8,500per year

Everything running, monitored, and supported by a dedicated team member.

  • Two way customer sync, unlimited records
  • Sales, products, employees, shops and registers
  • Polling as often as every five minutes
  • Conflict review and duplicate prevention
  • Support, Monday to Friday, 8:30am to 5:00pm Pacific

Custom work

Quoted

Insight can be customised to meet your exact needs. Bring the awkward requirement to the call.

  • Advanced or non standard field mapping
  • Multi shop and multi register rollouts
  • Migration and historical backfill planning

Questions before you commit? A dedicated team member is available Monday to Friday, 8:30am to 5:00pm Pacific.

Straight answers

The questions that come up on every call.

It depends on direction. Going from Lightspeed to Salesforce, Insight polls on an interval you set, and that interval can be as short as five minutes. Going from Salesforce to Lightspeed, an Account or Contact update is queued the moment it is saved and sent as fast as Lightspeed's API accepts it.
Customers do. Lightspeed Customers and Salesforce Accounts and Contacts are bidirectional. Sales and quotes, items, employees, registers and shops are fetched one way, from Lightspeed into Salesforce. A few individual fields are one way even within the customer record, and those are marked in the field mapping explorer above.
Insight compares the information inside a record before creating anything, which is what stops the same person turning up twice. Where the two systems genuinely disagree on a value, the record is flagged for review rather than silently overwritten.
Yes. If Person Accounts are enabled in your org, Insight uses the Person Account fields in place of the default Contact mapping. Two fields behave differently under Person Accounts: Company and Website do not sync. Every Person Account variant is listed in the explorer above.
Yes. Configuration decides what is in scope. If there is something you do not want synchronised, it will not be. That is worth walking through on a call, because scoping decisions are easier to make while looking at your actual records.
Insight is not able to sync Lightspeed R custom fields. Standard fields are covered thoroughly, and advanced mapping work can be quoted separately if your setup depends on something unusual.
Both. Insight works with Salesforce Classic and Lightning Experience.
They all queue and they all send, but Lightspeed's API sets the pace. If a very large number of Salesforce records are updated at once, you may notice the queue taking longer to drain. Worth flagging on the call if a bulk migration is part of your plan, so it can be sequenced properly.
Next step

Bring your messiest customer record.

Thirty minutes, screen shared, on your data. We will map your Lightspeed fields to your Salesforce org live and tell you honestly where the awkward parts are.

Open the calendar in a new tab
30 minutes Screen shared No slide deck Mon to Fri, 8:30am to 5:00pm Pacific