Home / Product / Import and export

Bring data in and keep an exit

Start with the data you have. Keep the freedom to take it with you.

Turn existing tabular data into application records, seed repeatable environments, and export the information your product creates.

See what it changes Technical guide ↗

Import and export in a product

Bring an existing datasetCSV, spreadsheet, or seed file

Turn it into connected recordsCreate or extend the application structure

Move data when you need itExport for review, migration, or downstream work

Your data has an arrival and an exit path

01Avoid a blank-slate migrationUse existing files to begin the application model.

02Create repeatable starting statesSeed development or demonstrations with declared data.

03Keep practical portabilityExport product data instead of trapping it behind a UI.

Why it matters

Adopting a backend should not mean re-entering everything by hand.

New products often begin in a spreadsheet. Existing products already have customers, content, or operational records that need a sensible path into the new system. Teams also need a way to inspect and move what the application later creates.

Daptin supports seed imports and actions that can create or extend a resource from CSV or spreadsheet-shaped input. Export paths produce common machine- and human-readable formats, including streaming options for larger result sets.

The result is a practical bridge into the application and an honest exit path. The data model, permissions, files, and external dependencies still need deliberate migration planning.

Turn prototypes into a starting model

Move useful spreadsheet structure into a backend instead of discarding it.

Recreate useful environments

Load declared sample or seed data for development and demonstration.

Preserve ownership

Extract schema and records for audits, downstream processing, or migration.

How it fits

Part of one connected backend.

Import and export does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Prepare

Clean the source and decide the intended record shape.

Step 2Import

Create records or add missing structure through a controlled action.

Step 3Use

The data joins the same APIs, permissions, files, and actions.

Step 4Export

Stream selected records into a format suited to the next job.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Spreadsheet-to-portal

Turn a member or inventory sheet into records behind a working application.

Demo environment

Load believable sample data every time a team starts a fresh instance.

Migration or reporting

Export selected data for another system, archive, or offline review.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes import and export more useful.

Know the boundary

What Daptin leaves in your hands.

Import cannot infer every business rule from a spreadsheet, and export alone is not a complete backup. Review types, relationships, access, file assets, secrets, and configuration as separate migration concerns.

Understand the operating responsibility →

Build from one foundation

Make import and export part of the product—not another disconnected service.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities