A scheduled export should refresh the records your team needs at the frequency its decisions require. LC Bridge’s early-access workflow is designed to save an import’s fields, filters, destination, and schedule. Each execution that transfers primary CRM records adds usage, including repeat transfers of the same records.
Choose freshness from the reporting decision
A daily operating review, a weekly client meeting, and a live sales handoff have different freshness needs. Start by writing down who reads the sheet and when. Then choose the least frequent schedule that still supports that work.
“Always current” is not a precise requirement. Specify the expected refresh interval and make the last successful transfer visible. A report viewed at noon should not look like a noon snapshot if its source last refreshed the previous evening.
Scope the data before scheduling it
A smaller relevant dataset is usually easier to inspect than an account-wide export. Select the objects, fields, and filters that answer the question. For appointments, use an intentional calendar and date window. For opportunities, preserve pipeline and owner context.
A filtered import is not an access-control boundary once data is in a shared workbook. Check who can open the destination sheet and whether the selected records belong there. Share the report with the same care you would share its underlying rows.
Understand execution-based usage
Repeated delivery of an existing record is still a transfer. If a job transfers 100 contacts on three executions, it produces 300 record transfers. This is a counting example, not a subscription price or a promise that every import uses full refreshes.
Refreshing a chart from data already in the worksheet is different from fetching source records again. The pricing page separates those actions and lets you explore records per execution and execution frequency. High-volume recurring work can be discussed as a custom subscription.
Keep configuration changes separate from data jobs
Renaming an import or saving a schedule should not be confused with running a source transfer. In the reviewed prototype, settings-only saves are separate from a run; field or filter edits require a current preview before Save & Run.
That distinction makes maintenance more predictable. It also prevents a harmless settings change from looking like a data refresh. Check the import’s actual last-run result rather than assuming that every Save button means fresh worksheet values.
Example: choose the refresh that answers the question
A team reviews 400 relevant opportunities on four weekly reporting runs. If each execution successfully transfers all 400 records, that workload creates 1,600 record transfers. Running the same 400-record import every day for 30 days creates 12,000 transfers. Reusing the same source IDs does not make those later executions free.
The right schedule depends on the decision. A weekly management meeting and a daily follow-up queue can need different freshness. Scope the import to the records that support that question, then review the expected transfer count in the calculator.
These are workload examples, not featured subscription prices. For a continuously refreshed dataset, discuss a custom subscription and agree its scope with LC Bridge.
Plan a visible recovery path
Connections expire, permissions change, and data can be unavailable. Keep the unfinished setup when asking somebody to reconnect. Preserve the previous successful delivery and show the error without inventing new zero totals.
After reconnecting, require an intentional retry. Do not automatically send outgoing CRM changes. Use the sample library and schedule documentation to evaluate the intended workflow while production access is being prepared.
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.