The Problem: How Do You Move One Excel Sheet Through Three Systems?
Many companies run their business like this:
- The sales team records client details and contract terms in Excel
- The backend system needs JSON data to integrate with the CRM
- The legal team needs to generate formal Word contracts from those same terms
The traditional approach: manually export three times, adjust formats individually. It’s slow, error-prone, and nobody enjoys it.
Let’s show you how to build a complete automated pipeline using three WTSolutions tools — turning one Excel sheet into data flowing through three systems seamlessly.
The Tool Stack
| Step | Tool | What It Does | Platforms |
|---|---|---|---|
| Step 1 | Excel-to-JSON | Excel spreadsheet → structured JSON | Web / Excel Add-in / WPS Add-in / Local App |
| Step 2 | Data Transfer | Push JSON to backend API | Any HTTP client |
| Step 3 | JSON-to-Excel | API response → Excel for review | Web / Excel Add-in / WPS Add-in / Local App |
| Step 4 | Sheet-to-Doc | Excel data → batch Word contracts | Web / Excel Add-in / WPS Add-in / Local App |
Step 1: Excel-to-JSON — Turn Your Spreadsheet into API-Ready Data
Imagine your sales team maintains a sheet like this:
| Client | Product | Quantity | Unit_Price | Total | Contract_ID |
|---|---|---|---|---|---|
| Shanghai ABC Corp | Cloud Service A | 50 | 2000 | 100000 | CT-2026-001 |
| Beijing XYZ Group | Cloud Service B | 30 | 3500 | 105000 | CT-2026-002 |
| … | … | … | … | … | … |
Open this in Excel-to-JSON, select “Flat Mode,” and click Convert. In seconds, you get:
1 | [ |
Push this JSON to your CRM or backend API via an HTTP POST request. If your system expects nested structures, switch to “Nested Mode” and set the delimiter to . — the tool generates multi-level JSON automatically.
Available platforms: Web app, Excel Add-in (Office 2013+/Office 365), WPS Add-in, REST API, MCP service, and local desktop application. No matter your environment, there’s an entry point for you.
Step 2: JSON-to-Excel — Bring API Data Back into a Spreadsheet
After your backend processes the data, you might need to bring results back into Excel for business colleagues to review or hand off to the next step.
JSON-to-Excel supports three input methods:
- Paste — Paste JSON text directly
- Upload — Upload
.jsonor.jsonlfiles - URL Load — Enter an API endpoint URL and let the tool fetch data automatically
Customization options include:
- Max nesting depth: 1-20 levels or unlimited; deeper levels auto-convert to strings
- Empty value handling: Empty string, null, or exclude
- Boolean format: true/false, “true”/“false”, or 1/0
The output Excel file can be handed to a colleague or fed directly into Sheet-to-Doc.
Step 3: Sheet-to-Doc — Batch-Generate Word Contracts from Excel
Now your Excel data needs to become formal contracts. This is exactly what Sheet-to-Doc excels at.
- Prepare a Word contract template with
{Client}{Product}{Total}as placeholders - Open Sheet-to-Doc and upload your template
- Paste your Excel data or upload the file
- Set filename rule:
Contract_{Client}_{Contract_ID}.docx - Click “Generate”
Within seconds, you get a ZIP file with Word contracts named by client. 1000 contracts? Same timeline — just a few minutes.
Pro Tip: Loop Placeholders for Multi-Product Contracts
If a single contract has multiple product line items, Sheet-to-Doc’s Loop Placeholders handle it elegantly:
1 | Contract: {Contract_ID} |
Combined with nested-mode JSON from Excel-to-JSON, a single data row generates a contract with multiple itemized rows.
The Full Pipeline: Before vs. After
| Task | Manual Process | Tool Pipeline |
|---|---|---|
| Excel → JSON | Manually format JSON | One-click, seconds |
| JSON → API | Copy-paste into API docs | HTTP POST, automated |
| API → Excel | Manually reorganize results | JSON-to-Excel, instant |
| Excel → Word | Copy-paste row by row | Batch generate, thousands in minutes |
| Total (1000 records) | ~8 hours | ~10 minutes |
Data Security Throughout the Pipeline
All three tools support local processing — data never leaves your device:
- Excel-to-JSON: Local desktop version runs fully offline
- JSON-to-Excel: Web version processes in-browser; local version works without internet
- Sheet-to-Doc: Browser-side processing; desktop version adds offline + document encryption
For sensitive data like contract amounts and client details, the local desktop versions are the safest choice.
Final Thoughts
Excel, JSON, and Word — three data formats that most businesses handle every single day. Instead of having colleagues manually shuffle between them, string them into an automated pipeline.
Excel-to-JSON gets data flowing. JSON-to-Excel brings it back organized. Sheet-to-Doc turns it into formal documents. Three tools, one pipeline, 1000 contracts, 10 minutes.
Start now: