A record-transfer model charges for successfully moving a primary CRM record during an execution. Moving the same record during another execution creates usage again. LC Bridge’s planned base rates include 250 transfers each month, then graduated per-transfer pricing, with custom subscriptions available for high-volume teams.
A transferred record is the unit
A contact, opportunity, or invoice is a primary business record when it is the selected output of a data operation. Its selected fields do not become separate commercial units. A contact with ten selected fields is one transferred contact, not ten transfers.
The identity of that record still matters for reliable delivery, but it does not exempt later executions from usage. Delivering a contact again is another transfer. This model is different from a monthly subscription that counts each distinct stored record once.
Repeated executions create repeated usage
If one execution successfully transfers 100 opportunities and another transfers the same 100, the two executions produce 200 record transfers. If only a different, smaller set is actually transferred, count that successfully transferred set. Do not infer the amount from a physical worksheet’s row count alone.
A chart recalculated from already delivered worksheet data does not fetch CRM records by itself. A source refresh that transfers records does. The distinction lets teams use their spreadsheet for analysis while choosing source refreshes intentionally.
Supporting rows do not multiply the parent charge
Invoices can contain multiple line items. The planned rule bundles those items with their parent invoice. An invoice-line report therefore counts the underlying transferred primary invoices rather than every rendered line.
Similarly, a label fetched only to describe another record is a supporting lookup. Selecting contacts as their own primary dataset is different from using a contact name to label a task. The data catalog and eventual production receipts need to preserve that distinction.
Discounts and retry protection answer different questions
The monthly allowance and graduated bands determine the price of accumulated transfers in an account. Retry protection identifies whether a delivery is the same operation being reconciled or a new execution.
A retry of the same operation must not create a duplicate charge. A new execution legitimately transferring the same records is new usage. Production billing must keep durable operation identities; the public calculator is an estimate, not a charging service.
Example: two executions are two transfers of the dataset
An invented account successfully transfers 100 primary contacts on an initial execution and the same 100 contacts on a later execution. That is 200 transfers. A third successful execution brings the account to 300 transfers. The 250-transfer allowance covers part of that total; 50 transfers enter the first paid band.
Retrying delivery from the same accepted operation must reuse its receipt and avoid a second charge for that operation. Starting a new transfer execution is different. Check the actual transfer result before starting another run, especially when an earlier delivery has an uncertain outcome.
Fields and bundled child rows do not change the primary-contact count in this example. Final charges use the agreed rates, applicable markup and tax.
Make high-volume costs predictable
The pricing page leads with 1.5¢ per additional record transferred, then shows the complete volume ladder. Rates decrease through the graduated bands. Base estimates exclude applicable account markup and tax.
If your team transfers large datasets frequently, Talk to Sales about a custom subscription. Bring your expected records per execution, frequency, and account count. We can discuss a predictable commercial arrangement without pretending that one generic subscription fits every workload.
Sources and further reading
Provider references checked October 16, 2026. Menu labels and source access can change. Product examples describe the reviewed early-access design.