AdemeroHelp

Export Paige documents to Laserfiche with Import Agent

Point Paige's SFTP export at a folder that Laserfiche Import Agent watches, and every finished document is filed into the repository with a template and tags assigned — for self-hosted Laserfiche or Laserfiche Cloud, with no automation platform. Paige's per-document field values stay in its data files for Laserfiche to fill in its own way.

Administrators1 hourVerified 2026-09-05

Before you begin

  • Laserfiche Import Agent installed on a Windows machine that can reach the repository (self-hosted or Cloud), with a license
  • A Laserfiche account for the import — for Laserfiche Cloud, a service principal
  • An SFTP server whose folder the Import Agent machine can reach by a local or UNC path
  • A Paige scan job with document types set up

At the end of this guide, every document Paige finishes is filed into your Laserfiche repository by Import Agent — as a searchable PDF, in the folder you choose, with the template and tags your profile assigns — minutes after Paige exports it.

Be clear about what this path does and doesn't do. Import Agent assigns metadata from its profile: fixed values, tokens like the file name and date, a template, tags. It does not read Paige's .json or .xml for per-document values. If you want Paige's extracted fields in the template, use the Power Automate path; or take this path and let Laserfiche fill fields afterwards with Quick Fields, Workflow, or a person — the PDF Paige produces already has a text layer for those tools to read.

How it works

  1. Paige exports each finished document to an SFTP folder: a PDF, then .json, .xml, and .csv files with the same base name.

  2. Import Agent's profile monitors that folder for *.pdf, imports each PDF into the repository, and moves or deletes the source file.

  3. The data files stay behind (or get cleaned up on a schedule); they're useful if someone wants Paige's values later.

Step 1 — Prepare the folder

The Import Agent machine must reach the folder Paige writes to by a Windows path it can read and delete in. The simplest arrangement is an SFTP server on that same machine (Windows' built-in OpenSSH Server is enough) with the folder on a local drive, for example D:\PaigeImport\Invoices. A UNC share the Import Agent service account can reach also works.

Open port 22 inbound from Paige's address ranges — Outbound IP ranges for firewall allow-lists.

Use one folder per scan job; each becomes one Import Agent profile.

Step 2 — Point Paige at the folder

  1. In Paige, open Settings (the gear at the bottom of the left menu — administrators only), pick the scan job, and choose Export.

  2. Click the FTP card. Enter the server's FTP Address, Port 22, the SFTP account's Username and Password, and the folder in FTP Folder Path as the SFTP account sees it.

  3. Click Test Connection. What you should see: FTP connection successful! Connect — Connected to FTP Server! and a green Connected label.

  4. Turn on Enable Auto Export, switch on Only documents having a document type, set Human Reviewed to Reviewed if a person checks documents in Paige first, and click Save.

Step 3 — Create the Import Agent profile

  1. Open Laserfiche Import Agent Profile Manager from the Start menu and choose Profile > New. Name it for the scan job.

  2. When prompted for the account, enter the repository sign-in. For Laserfiche Cloud, use the Laserfiche Cloud tab with the account ID and a service principal's username and key rather than a person's login.

  3. General tab: set Monitored folder to the folder from Step 1 (full path or UNC), leave Retrieve files from subfolders off, and set the Filter to import only files whose names match *.pdf — this keeps the .json, .xml, and .csv files out of the repository.

  4. Properties tab: set the document Name (a naming convention using tokens such as %(FileName) — Paige's file names are unique but not meaningful, so consider adding %(Date)), the destination Folder, and the Volume.

  5. Fields tab: assign the template (for example Vendor Invoice) and any fixed field values that apply to every document from this scan job.

  6. Tags tab: add tags if you use them (a Scanned by Paige tag makes these documents easy to find later).

  7. Processing tab: leave OCR off — Paige's PDFs already carry a text layer; Laserfiche's full-text search will index it on import.

  8. Post-processing tab: choose Deleted for successfully imported files, and a folder for failed imports.

  9. Schedule tab: check Enable this profile and choose Continuously.

  10. Save the profile.

Step 4 — Test it

  1. Process one document through the scan job in Paige and wait for the export.

  2. Watch the monitored folder: the PDF appears and, within moments, disappears (Import Agent took it). The data files remain.

  3. In the Laserfiche client, open the destination folder. What you should see: the document, with your template and tags, text selectable. Search the repository for a word from the page — it's found.

Filling fields afterwards

Paige's values for each document are in the .json and .xml left in the folder. Two ways to use them without the API path:

  • Laserfiche Workflow on the document created event can read the matching data file (same base name, .xml) from the folder and set field values — the XPath for a Paige field is export/fields/field[@name='Invoice Number'].
  • Quick Fields can re-read values from the PDF's text layer using its own zones and pattern matching, which works well when the layout is consistent.

Or skip both and use the Power Automate path, which fills fields on import.

When it doesn't work

SymptomWhere to look
Files arrive but Import Agent never takes themThe profile isn't enabled, the schedule isn't continuous, or the service account can't read the monitored folder (UNC paths need a domain account, not Local System).
Files land in the failed-imports folderThe account lacks rights on the destination folder, or the template's required fields aren't satisfied by the profile. Check the Import Agent event log.
Data files pile upExpected — the filter excludes them. Clear them on a schedule, or import them too if you want them in the repository.
Nothing arrives from PaigeAuto-export criteria aren't met, or the document was processed before you turned auto export on. Export once from the Documents page.

If the Paige side is the problem, contact Ademero support with the scan job name and the message from Test Connection.