Docs/Insight and Delivery

CSV Exports and Destinations

CSV exports and destinations move records, properties and defects out of Manifold to a file or a configured cloud destination.

For: Data operations and customer success3 min read3 sections

Export path selector

Choose the right delivery method before configuring files or destinations.

Best for

A client or colleague needs a quick file for a specific date range.

Avoid

Do not use one-off CSVs as a hidden recurring process.

Use this process

  • Run a manual export of records, properties, or defects.
  • Match the date range preset to the report.
  • Send only to approved recipients.
Export exampleCustomer-safe walkthrough

Move approved data to the systems that need it

Run manual or scheduled exports of records, properties, and defects to SFTP and cloud destinations, with formula-injection-safe CSV and an audit trail.

What you see

  • Manual and scheduled exports with run history.
  • Destinations for SFTP, S3, GCS, Azure Blob, and SharePoint.
  • Status on each run, including failures to investigate.

How to use it

  • Validate a destination with a manual run before scheduling it.
  • Keep destination credentials server-side.
  • Use the date range preset (last 7, 30 or 90 days, this month, since last run, or all time) to control the window; gas exports have no status filter.
  • Review run status and investigate failures promptly.

Export operations

Destinations

3

Scheduled

4

Failures

1

Gas safety recordsSFTPDelivered
DefectsS3Delivered
PropertiesSharePointFailed

Decision guide

SituationRecommended actionProof it worked
One-off file for a clientRun a manual CSV export for the date range.The file matches the report.
Regular BI feedConfigure a scheduled export to the destination.Runs deliver on schedule.
A run failedCheck credentials and the path, and confirm the host is public.The next run delivers.

Troubleshooting path

  1. 1If a manual export is unavailable, confirm the entitlement and permission.
  2. 2If delivery fails, check credentials and the bucket or path, and confirm the host is public: internal, loopback and private-range addresses are blocked.
  3. 3If a scheduled export did not run, check the schedule and destination health.

Related docs

Analytics consoleSecurity, privacy, and data handlingReports and AI summaries

Export run log

CSV sample

Safe example data
Name,Triggered,Destination,Status,Rows,Started,Duration
Monthly BI feed,Scheduled,SFTP · agent-reports,completed,128,2026-06-01 06:00,4s
Ad hoc export,Manual,Download,completed,37,2026-06-01 06:02,2s
Monthly BI feed,Scheduled,SharePoint · Compliance,failed,0,2026-06-01 06:03,1s
A failed run usually means a destination credential or path problem. One gas run delivers three CSVs: records, property register and defects.
Re-run after fixing the destination rather than editing delivered files.

CSV Export Functions

CSV exports and destinations in Manifold move gas safety records, properties, and defects out of the console and into the tools your business already runs on: a one-off download for a single recipient, or a scheduled export that lands in a cloud destination automatically.

  • Run manual exports of gas safety records, properties, and defects.
  • Configure destinations for SFTP, Amazon S3, Google Cloud Storage, Azure Blob Storage, and SharePoint.
  • Create scheduled exports and review export runs.
  • CSV encoding is formula-injection-safe and exports are audited.
  • The Exports page lives at /exports (type it into the address bar; there is no sidebar link) and has four tabs: Export now, Scheduled, Destinations and History.
  • The gas export is one bundle of three CSVs: records, property register and defects. Records and defects follow the date range, the register is always a full snapshot, empty files are skipped, and several files download as a ZIP.
  • A manual export can be downloaded or sent straight to a saved destination. Schedules run daily, weekly or monthly at an hour in UTC.
  • Failed scheduled runs email owners, or owners and office staff, when Scheduled export failures is on under Settings, then Notifications.
  • Properties and Appliances lists also export selected rows to CSV, and Power BI users can read the live OData feed described under Public API.

Choosing an Export Destination Path

Manual and scheduled exports share the same underlying data and the same safe CSV encoding; the difference is only whether a person triggers the run or a schedule does it for them.

  • Use a one-off CSV for a quick file to a specific recipient for a date range.
  • Use a scheduled export when a downstream system needs regular delivery.
  • Validate a scheduled destination with a manual run before relying on it.
  • See CSV Imports and Templates for the equivalent bulk-loading path in the other direction.

Troubleshooting

  • "Manual exports are not included in this plan": confirm the entitlement; the Exports page itself is only available to owners and office users.
  • Destination delivery fails: check credentials, the bucket or path, and any network allowlist.
  • Scheduled export did not run: check the schedule, last run status, and destination health.

Destinations Reference

  • SFTP: deliver files to a host and path with a password or a private key, with optional host-key fingerprint pinning.
  • Amazon S3 (including a custom endpoint for R2 or MinIO), Google Cloud Storage, Azure Blob Storage: deliver to a bucket or container.
  • SharePoint: deliver into a document library for downstream teams.
  • Credentials are stored encrypted once saved; never paste them into notes or support tickets.

Was this page useful?

Previous

Reports and AI Summaries

Next

Client Portal