OneUploadAutomate the delivery of file-based data to Azure Blob Storage.
Specialist componentOneUpload is a lightweight component for moving completed file batches from local or network storage into Microsoft Azure Blob Storage. It is an optional, specialist part of data export and reporting projects, often alongside OneADE, rather than a standalone platform.
A simple, reliable hand-off to Azure.
Some data and reporting projects need completed on-premises file batches to arrive in Azure Blob Storage reliably, without the originating system having to implement Azure connectivity itself.
OneUpload was originally built for CSV exports consumed by a Qlik reporting process in Azure, and is used as a specialist component alongside data export and reporting work.
What OneUpload does.
Key capabilities
- Upload to Azure Blob Storage
- Watches local or UNC source folders
- A batch-ready trigger, so only complete batches are sent
- Completed and failed routing
- Transfer logging
- Can complement OneADE exports
Common uses
- CSV reporting feeds to Azure
- Qlik or analytics hand-off
- ERP extracts to cloud processes
- Azure data-lake style staging
- On-premises to cloud file delivery
- An optional output path for OneADE projects
Can be adapted: OneUpload can be used alongside OneADE as an Azure delivery path instead of, or in addition to, populating SQL. Other file types can be adapted where required; we confirm support for your files as part of the project.
Batch ready. Upload. Route. Log.
Watch
A Windows background service monitors a configured local or UNC source location.
Ready
A batch-ready marker file signals that a complete batch can be processed.
Upload
Files are staged and uploaded to the configured Azure Storage account and container.
Route
Each transfer is logged and files are moved to Completed or Error.
Where it runs and what it connects to.
We install, configure and support OneUpload as part of your wider system landscape, and shape each deployment around the systems you already use.
| Area | Detail |
|---|---|
| Deployment | Windows system service installed in your environment. |
| Configuration | Azure Storage account, access key and target container. |
| Status | Specialist, optional component, usually delivered as part of a wider project. |
Cloud data delivery, as part of a bigger picture.
A typical story: an ERP or OneADE export, through OneUpload, into Azure Blob Storage, then on to Qlik, analytics or downstream cloud processing.
OneADE creates the reporting dataset; OneUpload provides a simple Azure hand-off. For general file movement between servers and partners, OneBridge is the better fit.
OneADE
MultiValue data extraction to SQL
Find out more Available / supportedOneBridge
Automated file transfer
Find out more Modernisation & IntegrationERP Data Extraction, SQL & BI
Turn ERP data into reporting-ready SQL datasets.
Find out more Modernisation & IntegrationSystems Integration & APIs
Managed integrations that run complete processes, source to outcome.
Find out moreThis site is in development and this page will be updated shortly.
Need your data in Azure?
Tell us about your reporting or data project. We'll show you whether OneUpload fits as part of the solution.