Migrate ProjectSend to Cloud
Migrate from a self-hosted ProjectSend install. Same software, same team, no server work. Files, users, and client accounts all transfer in under 48 hours.
· Updated · By ProjectSend Team

Same software. Same team. You stop managing the server. If you run a self-hosted ProjectSend install today, migrating to ProjectSend Cloud means the team behind the open source project handles your migration -- users, files, client accounts, and permissions all come with you. Migration is free, takes under 48 hours, and your clients notice nothing different.
What actually migrates when you move to ProjectSend Cloud?
Your workspace users, client accounts, uploaded files, folder structure, and branding settings all transfer. Clients log in exactly as before and find their files in place. Here is the complete checklist:
- All workspace users and their roles
- All client accounts and their permissions
- Every uploaded file and the folder structure around it
- Project assignments and per-client access settings
- Portal branding -- your logo, portal name, and color scheme
- Email notification configuration, including custom SMTP settings
What stays behind: any custom PHP configuration, htaccess rules, or third-party scripts you built outside of core ProjectSend. Those are worth noting before you start. The team is upfront about what manual steps are involved -- and automated migration from other file-sharing services (Dropbox, ShareFile) is not available.
What do you need to prepare before starting?
Gather your database credentials and access to your files directory. You do not need to take your server offline during the migration -- the team works from a copy of your data, so your existing clients can keep using the portal while the move is in progress.
- Your current ProjectSend version number (visible under Admin > System information)
- A SQL dump of your ProjectSend database
- Your files directory (the upload/ folder) as a ZIP archive, or an accessible SFTP path
- Your SMTP settings if you use a custom email server (host, port, credentials)
- A note on any custom configuration you rely on -- PHP settings, htaccess rules, custom fields
If you are on an older version of ProjectSend, it helps to know where your installation stands before reaching out. The open source project has been actively maintained for over a decade and is available at projectsend.org. The Cloud team handles any version compatibility steps as part of the migration -- you do not need to upgrade your self-hosted install first.
How does the migration work?
The ProjectSend Cloud team migrates your data for you. You share your database export and files; they provision your dedicated tenant, validate that everything is intact, and hand control back to you. Most migrations complete in under 48 hours.
- Sign up at ProjectSend Cloud -- a migrated install with client accounts needs Pro or Business; the Free plan (a personal account on a shared site) does not include client accounts
- Contact the team from your customer portal to request a migration -- let them know you are coming from a self-hosted install
- Share your database export and files directory securely with the team
- The team creates your dedicated tenant, imports your data, and validates that users, files, and permissions are intact
- You review the migrated portal -- check a few clients, download a test file, confirm branding looks right
- Your self-hosted server stays up until you decide to decommission it -- there is no forced cutover
What stays the same for your clients?
From their perspective, nothing changes. Your portal keeps your logo, your colors, and your domain name. Clients log in the same way they always have and find their files exactly where they left them. Notification emails continue to arrive from your configured address.
On the infrastructure side, each Pro and Business tenant runs on its own dedicated database -- not a shared schema where your data sits alongside other customers. Your files and access logs are yours alone. Every tenant also gets daily automated backups, so there is always a restore point. You can see how the platform is built at how it works and review what the open source foundation means for how the software is licensed and developed.
Can your AI assistant use the migrated portal?
Yes -- and it is a cloud-only capability. Once you are on Pro or Business, you can connect Claude, ChatGPT, or another AI assistant to your portal via the built-in MCP connector. The assistant can upload files, share them by link, and report when a client downloads them. Every action the assistant takes is logged in your audit trail, clearly labeled as an AI assistant action. The self-hosted edition of ProjectSend does not include this connector. Read how to set it up at Connect your AI assistant.
What if you want to go back to self-hosting?
You can, at any time. Because ProjectSend is licensed under the GPLv2 -- not AGPL, not a commercial license with strings attached -- you can export all of your data and redeploy it on your own infrastructure whenever you choose. The same code that runs your portal on the cloud is available as open source.
The ProjectSend repository on GitHub has 2,000+ stars (as of September 2026) and is in active development, running in production at more than 4,000 self-hosted instances worldwide with over 4.8M Docker image downloads. If you ever decide the cloud option is not right for you, the team will help you export your data and point you back to the self-hosted path. The code is open. So is your exit. For a detailed side-by-side of hosted versus self-hosted trade-offs, read ProjectSend hosted vs. self-hosted and ProjectSend Cloud vs. ProjectSend.org.
How does pricing compare to running it yourself?
ProjectSend Cloud's Free plan is a personal account on a shared site -- 2 GB, a private link for every file, no client accounts, no portal of your own. A self-hosted install with existing clients moves to Pro. If all you need is to hand files over by link, the Free plan costs nothing: no credit card, no time limit.
Pro is $19 per month and covers up to 25 active client accounts, 100 GB of storage, and three workspace user seats. Additional client accounts beyond 25 are $0.40 each. Compare that to the running cost of a VPS, a managed domain, SSL, an email delivery service, and time spent on updates and backups. For many firms, Pro costs less than the infrastructure they were running -- with none of the operational overhead. See the full pricing breakdown. No contracts, no annual commitment. More guides on self-hosting, migration, and the open source project in Self-hosting & open source.
Frequently asked questions
- Does the migration cost anything?
- No. Migration from a self-hosted ProjectSend install to ProjectSend Cloud is free and typically completes in under 48 hours.
- Will my clients notice anything changed?
- No. Client accounts, files, and permissions all transfer. Clients log in the same way and find their files exactly where they left them.
- Can I go back to self-hosting after I migrate?
- Yes. ProjectSend is GPLv2 open source, so you can export your data and redeploy on your own server at any time. The code is open. So is your exit.
- What plan do I need after migrating?
- A migrated install includes client accounts, so you need Pro ($19/mo) or Business ($49/mo). The Free plan is a personal account on a shared site with no client accounts -- not designed for a migrated install with existing clients.
- Do I need to take my server offline during migration?
- No. The team works from a snapshot of your data. Your self-hosted install stays live until you confirm everything is working on the cloud side.
ProjectSend Team. Written by the people who build and maintain ProjectSend, the open source client file portal (since 2011), and run ProjectSend Cloud.
Got a file to send? Start with it.
Drop it on our home page and confirm your email — no account first, no card. On the free plan you get a private link to share it and 2 GB of space, for as long as you need the account.
Or ask Claude or ChatGPT to do it
Connect your assistant to your ProjectSend account and ask in plain words. Everything it does shows up in your account as done by your AI assistant.
- “Save this summary as a PDF and give me a private link for my client.”
- “Did anyone download the contract I shared on Monday?”
- “Create a client account for Dana at Acme and send her the Q3 report.”Pro and Business
Keep reading
- ProjectSend Cloud vs. ProjectSend.org
Learn how ProjectSend.org and ProjectSend Cloud are related, who builds them, what they share, and when the hosted version makes more sense than self-hosting.
- Open Source Client Portal Software
Open source client portals give you full auditability, a real exit, and no vendor lock-in. Here is what to look for and how ProjectSend fits in.
- ProjectSend Hosted vs Self-Hosted
Running ProjectSend on your own server is free forever. ProjectSend Cloud hands off the infrastructure without changing your data, your code, or your exit.