Import Existing Data
Move records from spreadsheets or another app into Agiled.
Use imports when you already have records in spreadsheets or another business app. Importing early helps dashboards, CRM, finance, projects, and reports show useful data from day one.
What You Can Import
Depending on the enabled modules, Agiled can import records such as:
- Contacts
- Accounts
- Deals
- Projects
- Tasks
- Products
- Employees
- Expenses
- Appointments
Some guided onboarding imports run inside the onboarding flow. Other imports are available from the related module or settings.
Import the foundation records first. Contacts, accounts, products, employees, and projects are usually safer to import before records that reference them, such as deals, invoices, tasks, expenses, appointments, or payroll-related data. This makes matching and cleanup easier because later imports can point to existing Agiled records.
Prepare the CSV
Before importing:
- Use one row per record.
- Keep column names clear.
- Remove duplicate rows.
- Use consistent date formats.
- Make sure required fields are filled.
- Keep related records easy to match, such as account names for contacts.
Also remove columns that are only useful in the old system, such as formulas, temporary notes, export metadata, hidden IDs you will not use, and test rows. Keep a backup copy of the original export before changing it.
Choose The Right Import Entry Point
Use module-specific imports when you are importing one kind of record and need the clearest mapping experience, such as contacts, accounts, deals, products, or employees. Use settings or guided import when you are moving a broader set of workspace data during setup.
If you are unsure, start with a small module-specific import. A clean import of 10 records is more useful than a large import that creates duplicates across the workspace.
Preview and Commit
Guided onboarding imports preview the CSV before committing records. Review the summary before importing. If the preview looks wrong, update the CSV and upload it again.
During preview, check:
- required fields are mapped
- dates and currency amounts display correctly
- status, owner, pipeline, stage, role, and category values match existing Agiled options
- relationship columns match the names or identifiers used in earlier imports
- sample rows do not include old-system test data
After Import
Open the related module and check a few imported records. Confirm names, amounts, statuses, owners, dates, and relationships before inviting the full team to work from the data.
Review records from the beginning, middle, and end of the import. If the CSV had different customer types, currencies, owners, regions, or date formats, spot check one row from each group.
Import In The Right Order
Import foundational records before dependent records. A typical order is contacts and accounts first, then products, projects, deals, tasks, expenses, appointments, or other records that reference them. This gives later imports existing records to match against and reduces duplicate cleanup.
If an import depends on users or employees, invite or create those people first so ownership and assignment fields can be mapped cleanly.
If The Import Looks Wrong
Stop before importing more files. Export or note the affected rows, decide whether the records can be cleaned up with bulk actions, and only rerun the corrected CSV after the bad mapping is understood.
Do not rerun the same full CSV repeatedly unless the import flow is designed to update existing records. Repeated imports can create duplicate contacts, accounts, products, or deals.