Devpilot
System

Import and Export

Overview of the Devpilot bulk import and export experience — what it will cover, the job lifecycle, and current availability.

Import and Export

Devpilot is adding a dedicated import and export area so that large data movements — for example, pulling in a list of sites from a spreadsheet or exporting activity logs for an audit — can run asynchronously and be monitored after the fact. This page explains what to expect, the job lifecycle the UI will follow, and where the feature stands today.

Coming soon. The bulk import and export flows are not yet rolled out in the Devpilot dashboard. The underlying plumbing is being built in stages and availability will be announced on the Changelog. In the meantime, the single-record import and export options inside each feature area (for example deployment exports from a workspace) continue to work as normal.

What will be imported or exported

Each job will track one kind of data, identified by its model type. The types planned for the first release are:

Model typeTypical use
SitesBulk-adding sites to a workspace, or taking a snapshot of existing sites.
UsersMoving users between environments, or exporting a membership list.
TasksExporting task lists for reporting.
Activity logsPulling audit trails out of Devpilot for long-term retention.
DeploymentsExporting deployment history for compliance or reporting.

A job will also be tagged with a process type that tells you the direction of the data flow:

  • Import — data is being brought into Devpilot from an uploaded file.
  • Export — data is being packaged out of Devpilot into a downloadable file.

Job lifecycle

Each job will move through a small set of statuses:

Pending

The job has been queued. No work has started yet. You can still cancel a pending job.

Processing

Devpilot is actively working through the rows. The UI shows a running processed count against the total items count so you can watch progress.

Completed

All rows were handled successfully. For exports, the generated file becomes available to download. For imports, the new records are visible in the related area of the dashboard.

Failed

Something went wrong. The job keeps an errors record and a logs record you can review to understand which rows did not make it.

What the list view will look like

When the feature ships, the Import and Export area will show a paginated list of jobs. Each row will expose:

FieldWhat it shows
DescriptionA human-readable label for the job.
Data typeWhich kind of data the job touches (for example sites, users, or activity logs).
Process typeImport or Export.
StatusPending, Processing, Completed, or Failed.
Items count / processed countTotal rows versus rows already handled.
Progress percentageProcessed rows as a share of the total.
CreatorThe Devpilot user who started the job.
Started at / completed atWhen work began and finished, and the duration in seconds.

Filtering the list

You will be able to narrow the list by any combination of the following:

  • Status — for example, only show failures.
  • Process type — only imports, or only exports.
  • Data type — for example, only deployment exports.
  • Search — match against the description, the data type, or the creator's name or email.

The list will be paginated (default 15 per page) and sorted newest first.

Actions you will be able to take on a job

Open the job details

See the full description, progress counts, timestamps, logs, and any errors captured while the job ran.

Cancel a pending or processing job

If you started a job in error, cancel it before it finishes. Already-completed jobs cannot be cancelled.

Download the source file

For jobs with an associated file (typically imports, and exports that have finished building), download the original upload or the produced export.

Downloads will honour the original filename and MIME type that the file was stored with, so CSVs come back as CSVs and ZIPs come back as ZIPs.

Statistics

The area will also surface a small statistics summary so you can see, at a glance, how many jobs you have run, how they break down by status, and your most recent activity (the last five jobs). This is useful for workspaces that run heavy imports or scheduled exports.

Troubleshooting (once live)

  • My file won't download — the underlying file may have been cleaned up or moved. Devpilot checks both local disk and S3; if neither has it, the UI will report that the file is not found. Re-run the export in that case.
  • My import failed — open the job, read the errors array, fix the offending rows in your source file, and start a new import.
  • My job is stuck on processing — check the Status page for incidents affecting import workers, then contact support if the job does not progress.

What to do in the meantime

Until the dashboard UI is live, use the purpose-built tools that already exist in Devpilot:

  • Export deployment history from a project's deployment list — each project already supports on-demand exports of its own data.
  • Export activity logs from the activity log views inside each workspace and project.
  • Reach out via the Contact page if you need a one-off bulk export for an audit or a migration — the team can run it for you.

Next steps