Visser Labs – WooCommerce Plugins

  1. Home
  2. Knowledge Base
  3. WooCommerce Store Exporter Deluxe
  4. How to export to FTP or SFTP in Store Exporter Deluxe

How to export to FTP or SFTP in Store Exporter Deluxe

If a supplier, marketplace, or accounting system expects your WooCommerce data dropped onto a server at a set time, emailing a file or downloading it by hand doesn’t scale. Store Exporter Deluxe can push a Scheduled Export straight to an FTP or SFTP server instead, so the file just lands where it needs to be, on its own, every time the schedule runs.

This article covers setting up the FTP / SFTP delivery method on a Scheduled Export: every field on the form, how to run the schedule once to confirm it connects before trusting it to a timer, and what the plugin’s error messages mean when a connection fails.

Prerequisites

RequirementDetails
PluginStore Exporter Deluxe is active and licensed
Scheduled exportYou’ve already created a Scheduled Export. For detailed instructions, see How to schedule exports in Store Exporter Deluxe
Server detailsHave the host, port, username, and password from your hosting or FTP provider ready before you start. Only password authentication is supported, see the note below if your SFTP server requires a private key

Choosing FTP / SFTP as the delivery method

  1. Open WooCommerce → Store Export → Scheduled Exports.
  2. Open the schedule you want to configure, or click New Schedule to create one.
  3. Click the Method step at the top of the form.
  4. Select the FTP / SFTP card.

Selecting it reveals an FTP / SFTP Settings panel below the delivery method cards.

The Method step with the FTP / SFTP delivery card selected, showing the FTP / SFTP Settings panel appearing below it

Configuring the connection

The FTP / SFTP Settings panel has these fields:

  • Protocol: choose FTP or SFTP. SFTP encrypts the connection over SSH and is the safer choice if your host offers it.
  • Host: the FTP or SFTP server’s address, for example ftp.example.com.
  • Port: the server’s connection port. Leave this blank to use the protocol’s usual default, which the field shows as placeholder text: 21 for FTP, 22 for SFTP.
  • Username: the account username your FTP or SFTP provider gave you.
  • Password: the account password. Once a schedule has a saved password, this field shows dots instead of the real value and a note that a password is already saved. Leave it blank to keep that saved password, or type a new one to replace it.
  • Remote Directory Path: the folder on the remote server to upload into, for example /exports/.
  • Filename (optional): overrides the name of the uploaded file. Leave it blank to use the export’s default filename.

The FTP / SFTP form supports username-and-password authentication only. It has no setting for a private key, so an SFTP server that requires a private key can’t be used with this form.

The FTP / SFTP Settings panel with the Protocol, Host, Username, and Password fields annotated

Once you’ve filled these in, click Create Schedule (or Save Schedule on an existing one) to save.

Testing the connection before you rely on the schedule

There’s no separate Test Connection button on the FTP / SFTP form. Instead, save the schedule with its connection details filled in, then trigger a real run on demand rather than waiting for its schedule to come around:

  1. On the Scheduled Exports screen, find the schedule you just saved.
  2. Open its row’s action menu (the ⋮ button) and click Execute Now.
  3. Watch the Recent Activity panel on the same screen. The run shows as In Progress, then updates to Completed or Failed.

A Completed status confirms the file reached your FTP or SFTP server. If it shows Failed, the exact reason is in the Audit Log:

  1. Open WooCommerce → Store Export → Settings and select the Audit Log section.
  2. Check that Enable Audit Log is on (it’s on by default) and that Scheduled Exports is not set to None. By default, every other level, including Minimal, captures Error Details, the field that holds the plugin’s exact error message.
  3. Open Audit Log in the Store Export sidebar and expand the failed run’s entry to read the error message. If there’s no entry for that run, correct the settings from step 2 and run Execute Now again.

The Recent Activity panel shows only whether a run passed or failed. The exact reason is in the Audit Log entry for that run. If a schedule sets its own Log level on its Advanced step, that level wins over the one in Settings.

The Audit Log settings section with Enable Audit Log turned on and the Scheduled Exports log level set to Minimal

Troubleshooting

“Login incorrect for user … on FTP server” or “SFTP login failed for user …”
Your username or password is wrong, or the account doesn’t have permission to log in from your server. Re-enter both on the Method step and save again. Remember that a blank Password field keeps whatever password is already saved. If you meant to change it, retype it before saving.
“There was a problem connecting to … via FTP”
Store Exporter Deluxe couldn’t reach the host at all on the FTP protocol. Double-check the Host and Port fields for typos, and confirm with your hosting or FTP provider that the server accepts connections on that port from outside their own network. Some hosts only allow FTP connections from specific IP addresses, which blocks the plugin’s server from connecting.
An SFTP run fails with a connection or timeout error
Store Exporter Deluxe couldn’t reach the SFTP server. Check the Host and Port fields (SFTP uses port 22 by default), and confirm with your hosting or SFTP provider that the server accepts SFTP connections from your site’s server.
“Could not change to the directory … on the FTP server …” (FTP) or “Could not find or create the remote directory …” / “Could not change to directory … on SFTP server …” (SFTP)
The path in Remote Directory Path doesn’t exist on the remote server. SFTP tries to create it automatically if your account has permission to. FTP does not create missing folders, so create the folder yourself first if you’re using plain FTP. Either way, confirm the exact path with whoever manages the remote server, including the leading slash, and check that your account has write access to it.
“Could not upload file to FTP” (FTP) or “Could not upload file … to SFTP server …” (SFTP)
The connection and login succeeded, but the upload itself failed, usually because the account has read access to the directory but not write access. Ask your hosting or FTP provider to confirm your account can write files there, not just list them.

FAQ

Which is better, FTP or SFTP?
Use SFTP if your server supports it. It encrypts the connection, including your username and password, over SSH. Plain FTP sends everything unencrypted, so only use it if your provider doesn’t offer SFTP.
Can I use FTPS (FTP over SSL) instead of plain FTP?
Not from this form. The Protocol choice is limited to FTP or SFTP.
Is FTP/SFTP delivery available in the free Store Exporter plugin?
No. Scheduled Exports, and the FTP / SFTP delivery method along with it, are a Store Exporter Deluxe feature. The free Store Exporter plugin doesn’t include scheduled exports.
Does the remote directory need to exist before I run the schedule?
It depends on the protocol. On an SFTP connection, Store Exporter Deluxe creates a missing Remote Directory Path for you if your account has permission to create folders. On plain FTP, the folder must exist first, so create it before the first run.

Need more help?

If you’re using Store Exporter Deluxe and run into an issue this article doesn’t cover, open a support ticket and our team will help you get your export delivered.

If you’re using the free Store Exporter plugin, ask on the WordPress.org support forum and our team will get back to you there.

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support

PO BOX 4362 Gumdale QLD
Australia

ABN: 51 604 474 213

Products
Resources & Help
Our Brands

© 2026 Rymera Web Co Pty Ltd. All Rights Reserved. All prices are in USD.