Automating On-Prem -> BOX Uploads
Business Applications Specialist (Technical Product Manager) - Doctors of BC | 2025
Problem Statement
Our organization uses Box as the system of record for document storage, but core systems are hosted on air-gapped on-prem servers. This required manual document uploads from internal users — a time-consuming and error-prone process.
- No collaboration or less productivity
- High effort cost across teams
- Dependency on another legacy system to email sensitive information
- Compliance and audit risks
Solution
Developed a prototype using the BOX CLI:
- Created root folder and nested structure by convention
- Uploaded CSV files programmatically from a SQL server
- Replaced files with new versions
- Generated shareable links
- Schedule uploads via macOS (In Progress)
- Apply metadata to classify documents (In Progress)
Architecture Overview
[OnPremise System - SQL Server]
|
v
[Run BCP query via Powershell to download CSV files - Scheduled]
|
v
[Save files to a watched folder, monitored by another Powershell script that triggers BOX CLI commands]
|
Triggers Upload calls (insert/update)
|
v
[BOX Desination Folder]
|
V
[Update MetaData and Shareable Links]
Tech Stack
- Powershell
- Node.js/Bash(macOS)
- BOX CLI
- OAuth (JWT)
- SQL Server
Value Delivered
| Metric | Before | After |
|---|---|---|
| Manual Uploads | 60/month | 10 revisions/month |
| Upload Success rate | 60%+ | < 95% |
| Stakeholder Time Saved | 2–3 days | 5+ hrs/week |
| Intervention Required | 1 on-prem system | None |