External accounts
Every customer, contractor, and one-time recipient can create provisioning, password-reset, scope, and offboarding work.
How to replace FTP for external file transfers
Replace the human workflow, not every protocol. Use a live transfer link for one-time outbound delivery, a focused and instant upload link for inbound files, and managed encrypted storage when files must remain available. Keep SFTP where scripts, scheduled jobs, or partner systems require protocol-level automation.
PhotonFile maps those human-driven jobs to Relay, Secure Inbox, and Vault, reducing external account provisioning, shared credentials, server maintenance, firewall exposure, and client-software support.
Replace workflows, not protocols
SFTP can remain the right tool for system-to-system transfer, scheduled automation, existing scripts, and partners that mandate a protocol. PhotonFile is the stronger fit for people sending, receiving, or retaining external files without operating an FTP service.
Why human-driven FTP becomes expensive
Shared credentials
A common username is easy to forward and difficult to attribute, rotate, or retire without affecting everyone.
Server maintenance
Patching, storage, certificates, monitoring, backups, logs, and incident response remain your responsibility.
Firewall exposure
An externally reachable service adds network configuration, scanning, hardening, and exception-management work.
Client software
Users need the right client, host, port, path, mode, credentials, and local permissions before they can move a file.
Mixed retention
A one-time delivery and a persistent shared directory often end up on the same server with no clear lifecycle.
Where FTP/SFTP and PhotonFile fit
| Scenario | FTP/SFTP | PhotonFile workflow |
|---|---|---|
| Scheduled system export | Often the better fit when an integration already exists | Not positioned as a replacement for every automated protocol flow |
| One-time outbound delivery | Requires an account or shared drop location | Relay creates a live recipient link without long-term hosting |
| External person uploads files | Requires credentials, path instructions, and often a client | Secure Inbox provides a focused and instant upload page without browse access |
| Files must remain available | Persistent directories require permission and cleanup administration | Vault provides retained encrypted storage, scoped sharing and optional automatic cleanup when enabled. |
| Ad hoc contractor exchange | Account creation and offboarding repeat for short engagements | Choose Relay, Secure Inbox, or Vault based on the direction and retention need |
Map each FTP job to a smaller workflow
Outbound now
Relay moves the file
Use a live Relay session when a person is ready to receive a one-time file. The link is for the active handoff, not a permanent directory.
Inbound from outside
Secure Inbox collects the file
Give senders instructions and an upload link. They can submit files and notes without browsing the destination Vault.
Persistent access
Vault keeps the file
Use Vault when files, folders, versions, or managed shares need to remain available after the transfer.
A practical migration plan
- 1. Inventory the FTP workflows. Record owner, direction, users, automation, frequency, data sensitivity, retention, and integration dependencies.
- 2. Separate automation from human use. Keep scheduled and system-to-system SFTP jobs out of the first migration wave unless the replacement supports the same contract.
- 3. Map human jobs. Use Relay for outbound live delivery, Secure Inbox for external intake, and Vault for retained access.
- 4. Pilot with one partner. Choose a real but recoverable workflow, document the new steps, and measure support requests and completion time.
- 5. Remove shared credentials. Rotate or disable common accounts after the pilot, and close firewall or directory paths that no longer serve a workflow.
- 6. Update operating procedures. Document link handling, access codes, retention ownership, failed transfers, offboarding, and where automation remains on SFTP.
Security is more than transport encryption
SFTP protects a connection, but the surrounding workflow still needs identity, least privilege, offboarding, logging, retention, and recovery. A shared credential over an encrypted connection is still a shared credential.
For PhotonFile, use client-side encryption where supported, protect links and access codes, scope Vault shares, and maintain account and recovery controls.
Do not force one tool onto every transfer
A protocol integration, live handoff, external intake page, and persistent workspace have different failure modes. The operational goal is to give each job the smallest workflow that satisfies it.
That is the difference between replacing an FTP server and simply moving the same complexity somewhere else.
Common questions
Frequently asked questions
Is PhotonFile a replacement for every SFTP workflow?
No. Keep SFTP where scripts, scheduled jobs, system integrations, or partner requirements depend on the protocol. PhotonFile is positioned for human-driven delivery, intake, and retained sharing.
How do I replace an FTP drop box for customer uploads?
Create a Secure Inbox with instructions, sender notes, access controls, and notifications. The sender receives an upload page without browse access to existing Vault content.
How do I replace FTP for one-time outbound files?
Use Relay when both people can complete a live handoff. Use File Pass for a qualifying later pickup when offered, or Vault when the file must remain available.
What happens to shared FTP credentials?
Migrate the workflow first, then rotate or disable shared accounts and remove unused firewall or directory access. Do not leave the old path active indefinitely.
Can recipients use Relay without a PhotonFile account?
PhotonFile download flows do not require the recipient to create a PhotonFile account, including Relay receives.
Should persistent shared folders move to Vault?
Vault is the better PhotonFile fit when files need retained encrypted storage and scoped sharing. Review capacity, retention, team access, and recovery before migration.
Keep going
Related guides
Receive files securely from clients
Replace upload accounts with a focused intake boundary for sensitive documents.
Collect large customer uploads
Add packaging, retry, notification, and triage rules to external intake.
Send sensitive documents securely
Map recipient verification and retention controls into the replacement workflow.
Product and technical references: Relay guide Secure Inbox overview Vault overview PhotonFile Desktop
Pilot one human-driven FTP workflow
Choose a one-time outbound delivery or external upload process, map it to Relay or Secure Inbox, and keep automated SFTP integrations outside the pilot.