Full and incremental pulls

Refresh what changed without hiding the limits

Datplan can use the last saved position or checkpoint where a source endpoint supports it, reducing unnecessary repeat downloads while preserving a controlled full re-pull option.

Full re-pull

Best for a deliberate clean rebuild. It can use more allowance and provider quota, so use it for stale or incomplete data, material source changes or support-led recovery.

Review the evidence

A successful button click is not the whole result

Endpoint results

See which endpoint completed, returned no data, was skipped or reported an issue.

Run summary

Review downloaded volume, completion state and notes that may affect the reporting dataset.

Reconciliation output

Compare the pull and transformed output where the source workflow provides reconciliation evidence.

Diagnostics

Export sanitised run reports and diagnostic ZIP files for support without casually sharing raw business data.

Sync questions

When a smaller pull is—and is not—appropriate

Does every source endpoint support incremental sync?

No. Datplan uses the saved checkpoint only where the provider and endpoint support a reliable incremental behaviour. Other data may need a full or provider-specific refresh.

Does incremental sync avoid plan or provider limits?

No. It can reduce repeated download volume, but all pulls remain subject to Datplan allowances, provider quotas, permissions and service availability.

When should I use a full re-pull?

Use it when local data appears incomplete or stale, a schema or source state has materially changed, or Datplan support recommends a clean rebuild. A standard sync is preferable for routine work.

See Datplan with real reporting data—without connecting a live account

The Windows app is free to download and includes Datplan Demo data, so you can test sync, dashboards, reporting grains and exports first.