Manual Migration (Projects, Clients, Files)
What isn't bulk-importable today — and how to bring it over cleanly by hand.
#At a glance
| Detail | Value |
|---|---|
| Audience | Admins, department leads |
| Estimated time | Depends on volume |
| Portal areas used | Projects, CRM, Storage (manual) |
| AI used | None (manual) |
#Purpose
Set correct expectations: projects, clients, and files are created/uploaded manually, not bulk-imported.
#Business outcome
Non-lead data is migrated deliberately, starting with what's active, without waiting on imports that don't exist.
#Implementation checklist
1
Recreate active clients and projects manually in the platform
2
Upload only the files you actively need (no bulk file import)
3
Prioritize live work; archive the rest in your old system
4
Record decisions so nothing is assumed migrated
#Dependencies
- Leads imported
- A list of active clients/projects
#Risks
Watch for these
- Expecting a bulk importer for projects/clients/files (there isn't one)
- Trying to migrate everything instead of what's active
#Success criteria
Done looks like
- Active clients and projects exist in the platform
- Needed files are uploaded
- Everyone knows what was and wasn't migrated
#Related documentation
Importing Leads
What can import.
Storage & Media
How files are stored.
Contact Support
Reach the DevSphere OS team.
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?