Why this backup ran slowly — and why it isn’t a Control‑C issue

Control‑C backs up your Xero data entirely through Xero’s official API, using the same interfaces available to every approved Xero app. This means the maximum speed of any backup is fundamentally governed by Xero’s API behaviour, not by Control‑C’s infrastructure.

What actually determines backup speed

Xero’s API enforces:

  • Strict rate limits on how many requests can be made per organisation and per app
  • Throttling under load, particularly for reports, history, and large transactional datasets
  • Sequential access requirements for certain objects (e.g. invoices, invoice histories, payments), which prevents bulk parallel extraction

When those limits are reached, Xero intentionally slows or pauses responses. Control‑C must respect those limits to remain compliant and reliable.

In other words: Control‑C cannot “go faster” than Xero allows—doing so would risk incomplete data, API errors, or app suspension.

What Control‑C controls (and optimises)

Control‑C’s platform:

  • Efficiently queues and retries requests within Xero’s allowed thresholds
  • Preserves data integrity by backing up every object and every version (including historical changes)
  • Automatically resumes backups when Xero lifts throttling or capacity constraints

When a backup appears slow, Control‑C is typically waiting on Xero to release capacity, not processing data locally.

Why some backups are slower than others

You’re more likely to see slower backups if:

  • The organisation has a large or long historical dataset
  • Many invoices have frequent edits or approvals (more history to retrieve)
  • Xero is experiencing high regional API load
  • The backup coincides with Xero maintenance or peak usage windows

These factors all sit outside Control‑C’s control, but Control‑C is designed to handle them safely and automatically.

The bottom line

  • Control‑C is not failing, stalled, or under‑provisioned
  • The backup is progressing correctly, at the pace permitted by Xero
  • Slowness reflects Xero API constraints, not Control‑C performance

This is the trade‑off of a compliant, API‑driven backup: accuracy and completeness over speed shortcuts.