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.
Before importing
When migration is available for your workspace, sign up on the new platform with the same email used in classic Agiled and verify it. Settings > Legacy Import can then show eligible classic companies and brands to claim. Claim the intended workspace before requesting its data.
Each classic company or brand is a separate workspace. A claim does not copy the old password. If the expected workspace is missing, blocked, or under billing review, contact support with its name and your verified email; do not create a second import to work around the status.
Reseller-managed accounts require support review. Do not assume that a parent or reseller account automatically grants access to all child workspaces.
Request Import
- Open Settings.
- Go to Legacy Import.
- Review the linked legacy company.
- Select every module you intend to import.
- Check the record counts and status labels.
- Select Request import.
The data migration is a one-time import for the organization. Queued or running imports lock the selection, and a completed import cannot be extended with more modules. Review the full module list before requesting it.
Assign reviewers before requesting a broad import. CRM, finance, projects, files, scheduling, tickets, and attributes may each need a different person to verify the imported data.
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 before the one-time request. Queued, running, and completed requests lock the selection.
Module dependencies and Flow conversion
Some selections include prerequisite data: Files also needs CRM, projects/tasks, and tickets; Tickets needs CRM; Attributes needs CRM, finance, and projects/tasks. Review the full selection before the one-time request.
The separate legacy Flow conversion creates draft templates for review. It does not mean the data importer transfers all legacy workflows or makes converted templates ready to publish.
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.
- Record any count or mapping problem for support; do not try to create a second import.
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 contacting support. That evidence makes the review faster.