Request A Legacy Import
Select legacy modules and queue an import request.
Legacy import is used when a workspace has data available from an older Agiled system.
Only use this page when the workspace is linked to a legacy company. If no legacy company is linked, the page shows that no legacy source is available.
Request Import
- Open Settings.
- Go to Legacy Import.
- Review the linked legacy company.
- Select the modules to import.
- Check the record counts and status labels.
- Select Request import.
Imported modules are locked from being requested again. Queued or running imports must finish before another request can be made.
Request only the modules you are ready to review. A broad import can create a large cleanup queue across CRM, finance, projects, files, and scheduling.
Run the smallest useful import first when possible. Start with a module your team can verify quickly, then request additional modules after the review process is clear.
Supported Modules
Legacy import can request these module groups when data is available:
- CRM: accounts, contacts, deals, notes, tasks, and activity logs.
- Finance: products, taxes, invoices, estimates, payments, and expenses.
- Projects & Tasks: projects, project tasks, milestones, and time entries.
- Files: folder structure and file references.
- Scheduling: event types, availability, appointments, and calendar blocks.
- Tickets: support tickets and replies.
- Attributes: legacy custom fields and values.
Each row shows the module label, description, record count, and status. Available modules can be selected. Imported modules cannot be selected again. Queued or running requests lock the selection until the run finishes.
Skipped Modules
Review skipped modules to understand which data will not migrate and why.
Currently skipped groups include docs and proposals, wikis, forms, and workflows. Those areas use newer structures in the current app, so they should be rebuilt or recreated instead of imported directly.
Plan time to rebuild skipped areas before telling the team migration is complete. Imported records and rebuilt processes often need to be connected manually.
After Requesting Import
- Wait for the status to move out of queued or running.
- Review imported modules in the app.
- Spot-check record counts and important customer records.
- Rebuild skipped docs, forms, and workflows in the current app.
- Avoid requesting another import until the current request is complete.
Assign reviewers before the import starts. CRM, finance, projects, files, scheduling, tickets, and attributes usually need different people to confirm whether the imported data is usable.
Post-Import Review
Review one high-value record from each imported module. For example, check one account, contact, invoice, payment, project, file, appointment, ticket, and custom field before the team starts using imported data.
Compare counts with the legacy source, then mark cleanup tasks for duplicates, missing owners, old statuses, broken file references, or stale custom fields.
Before Using Imported Data
Imported data may need cleanup. Review contacts, finance records, project tasks, file links, scheduling records, and attributes before relying on them for customer communication or billing.
Tag or save views for imported records where possible. This makes post-import review and cleanup easier to coordinate.
Do not send invoices, booking links, or customer emails from imported records until the relevant customer, finance, and communication fields have been checked.
If imported counts do not match the legacy source, record the module, count, sample record, and import run time before requesting another import. That evidence makes the next review faster.