Agiled Docs

Use this guide when your team currently tracks work in spreadsheets and wants to move into Agiled without losing context.

Treat migration as a cleanup project. Importing messy spreadsheets usually creates messy CRM and project data.

Assign an owner for each module before importing. CRM, finance, delivery, and HRM data each need someone who can judge whether the imported records are usable.

Prepare Your Spreadsheets

Split data by record type: contacts, accounts, deals, products, projects, tasks, employees, expenses, and time entries.
Remove duplicate rows.
Standardize dates, currencies, phone numbers, and email addresses.
Add clear column headings.
Keep a backup copy of the original files.

Remove formulas, merged cells, hidden columns, and temporary notes before import. Convert values to plain text, numbers, or dates that can be mapped reliably.

Create one column for each field you want to map. Do not combine first name, last name, company, phone, tags, and notes into one cell unless you are willing to clean that data manually after import.

Import Order

Import contacts and accounts first.
Import deals after contacts/accounts exist.
Import products before creating invoices or checkout links.
Import projects before tasks.
Import HRM records before attendance, leave, or payroll data.
Import finance history only after numbering, currency, taxes, and payment settings are reviewed.

Use small sample imports first. Validate field mapping and relationships before importing the full spreadsheet.

Use 5 to 20 representative rows for the first sample. Include normal records, records with optional fields, and one or two edge cases so you can test mapping without creating a large cleanup job.

Do not import everything at once just because the file is ready. Importing in module order makes relationship errors easier to catch before they spread.

After Importing

Review import failures.
Spot-check important records.
Confirm relationships between contacts, accounts, deals, projects, and tasks.
Clean up custom fields and saved views.
Archive the spreadsheet once Agiled becomes the source of truth.

Decide The Source Of Truth

Pick the date when Agiled becomes the system of record. After that point, avoid editing old spreadsheets except as archived references.

Migration Checks

Compare record counts, spot-check important customers, confirm linked accounts and contacts, and review reports for obvious outliers before the team depends on the imported data.

Ask each module owner to review their area before announcing the migration. CRM should review contacts/accounts/deals, finance should review products and historical billing context, delivery should review projects/tasks, and HR should review employee records.

Go-Live Checklist

Before the team starts using Agiled as the source of truth:

Compare record counts with the original spreadsheets.
Spot-check high-value customers and active work.
Confirm owners and statuses.
Confirm imports did not create duplicate records.
Tell the team which spreadsheets are now archived.

Common Migration Mistakes

Avoid importing duplicate contacts from multiple sheets, using old owner names that do not match Agiled users, importing test rows, mapping notes into the wrong field, and importing finance records before tax, currency, and numbering settings are ready.

Move from Spreadsheets to Agiled