Agiled Docs

Imports help move existing data into Agiled.

Import Options

Agiled has two import paths:

CSV imports inside modules such as CRM, products, projects, tasks, employees, and expenses when that module exposes an import action.
Legacy import in Settings for workspaces connected to an older Agiled company source.

Use the module import when you have a spreadsheet. Use legacy import when the workspace has an available legacy company and you want Agiled to queue migration work from that source.

Prepare A CSV Import

Before importing a spreadsheet:

Export the source data as CSV.
Keep one record per row.
Put field names in the first row.
Remove duplicate columns.
Keep required values, such as contact name or email, in separate columns.
Use consistent date, currency, and status values.
Save a copy of the original file before editing.

For CRM imports, keep contact fields such as first name, last name, email, phone, company, title, address, tags, and owner in separate columns where possible. Cleaner columns make mapping easier and reduce failed rows.

Run A Module CSV Import

Open the module that owns the records.
Select the import action.
Upload the CSV file.
Map each source column to the matching Agiled field.
Preview the rows before committing the import.
Fix obvious mapping issues before creating records.
Complete the import and review the result.

If a field has no matching destination, leave it unmapped or create a custom attribute first when the data should be stored in Agiled.

Legacy Import

Open Settings → Legacy Import to review old workspace data that can be migrated.

The page shows:

the connected legacy company ID, when available;
importable modules with record counts;
module status, such as available, queued, or imported;
skipped modules that are not migrated and the reason they are skipped;
the requested date when an import has already been queued.

Request A Legacy Import

Open Settings → Legacy Import.
Confirm the legacy company shown on the page is the expected source.
Select the modules you want to import.
Leave already imported modules unchanged.
Select Request import.
Wait for the status to change to queued or running.

While an import is queued or running, the module checkboxes and request button are locked. This prevents duplicate requests for the same migration work.

Review Import Runs

After importing, review the result in the module or import run history where available. Failed rows should be fixed in the source file and reimported after correction.

Common causes of failed rows include missing required names, invalid emails, bad date formats, duplicate unique values, and values that do not match the workspace's configured statuses or stages.

Fix Failed Imports

Download or review the failed row details.
Correct the original CSV rather than editing only the failed output.
Remove rows that imported successfully if you are reusing the same file.
Re-run the import with the corrected rows.
Spot-check several imported records in the destination module.

For large imports, test with a small file first. Confirm the mapped fields and record layout are correct before importing the full dataset.

Imports

On this page