The result: Barberry Labs inventoried approximately 1,092 SYSPRO tables, identified and mapped the records required by Zoho, and used Zoho MCP with least-privilege permissions for approved Books, Inventory and CRM migration actions. Klara reduced repeated discovery and coordination work, saving approximately 336 hours of consulting effort, while finance and operations retained approval of mappings, opening balances and go-live.
Consulting effort saved: approximately 336 hours.
What changed for the business
The company needed a reliable route from a large, long-running ERP estate into Zoho. The delivery had to reduce dependence on repeated expert meetings without weakening finance control.
| Manual approach | Delivered approach |
|---|---|
| Senior specialists repeatedly search for the right source data | Klara creates a shared inventory of the required records |
| Frequent meetings to answer the same discovery questions | Finance and operations receive concise evidence for decisions |
| Mappings change while data is already moving | Mappings and acceptance rules are agreed before loading |
| Progress depends on one technical expert | Approved Zoho actions run through least-privilege MCP while finance reviews defined stages |
Executive outcome: discovery and preparation moved faster, while finance retained control of the decisions that affect reporting, stock, balances and cutover.
Effort comparison
The comparison below reflects the work completed for this SYSPRO-to-Zoho migration.
| Work | Manual approach | Klara-assisted delivery | Time saved |
|---|---|---|---|
| Find and catalogue the required source data | ~120–200 h | ~24–40 h | ~100–160 h |
| Map finance, customer, supplier and stock records | ~80–120 h | ~32–48 h | ~50–70 h |
| Define repeatable migration steps | ~64–96 h | ~24–32 h | ~40–65 h |
| Coordinate reviewers and decisions | ~64–96 h | ~16–24 h | ~50–70 h |
| Reconcile records before go-live | ~40–64 h | ~16–24 h | ~25–40 h |
| Total | ~480 h (~60 days) | ~144 h (~18 days) | ~336 hours |
Approximately 336 hours of consulting effort were saved on this migration.
Executive outcome: finance spent its time approving mappings, balances and exceptions—not paying for repeated technical discovery.
The business problem
A manufacturer with a live SYSPRO estate needed Zoho Books, Zoho Inventory, and CRM on a fast-track cadence (target go-live early August, hard stop end of August). Scope highlights for a serious Zoho Books data migration:
- ~140 active GL accounts (chart of accounts migration)
- ~300 suppliers / ~480 customers / ~460 CRM contacts
- Zoho Inventory migration with FIFO, 2 warehouses, and 8 product-list configurations
- Multi-currency (ZAR plus majors)
- Careful opening balances migration
The source database contained on the order of 1,000+ base tables. Blind CSV dumps are how AR ageings go wrong.
How the migration was delivered
1. One controlled migration workspace
The project used one controlled workspace for:
- Progress, decisions and exceptions
- Defined approvals from source access through testing and cutover
- Focused review packs for finance, inventory, operations and system owners
Nobody needs a recurring “status hour” to learn what Klara already recorded in the shared project record.
2. Fast discovery without disrupting the live ERP
Live discovery (sanitised samples):
| Area | Example volume |
|---|---|
| GL transactions | ~2.3 million rows |
| Sales order lines | ~844 thousand rows |
| Stock master | ~5.2 thousand items |
| Tables inventoried | ~1,092 |
This moved the conversation from finding data to approving what each record means and how it should appear in Zoho.
3. Prepare Zoho before cutover
The team agreed the load order, warehouse structure, product-list configurations and acceptance checks before production cutover. Klara used Zoho MCP with least-privilege permissions to perform only the approved migration actions. Pilot actions and record totals were reconciled before the scope expanded.
4. Business owners retain approval
| Seat | Job |
|---|---|
| Business process owner | How the business really uses modules |
| Source-system owner | Safe access and source-record accuracy |
| Finance reviewer | Accounts and opening balances acceptance |
| Migration delivery team | Approved MCP actions against signed mappings |
| PM | Cutover accountability |
The agent drafts questions and packs evidence. It does not invent VAT treatment.
Controls retained throughout the migration
- Source access was read-only.
- Zoho MCP permissions followed least privilege and were limited to approved migration actions.
- Credentials and extracts stayed inside the controlled customer environment.
- Test migrations were reconciled before production cutover.
- Finance approved balances, tax treatment and account mappings.
- Operations approved warehouse, stock and customer rules.
The approval path to go-live
What executives should take from this
- Capture source-system knowledge once instead of paying to rediscover it in meetings.
- A successful Zoho migration depends on approved mappings and opening balances.
- Make finance and operations approvals explicit in the delivery plan.
- Use least-privilege MCP permissions instead of broad administrator access.
- Use AI to remove repetitive work—not to bypass accountability.
Explore the migration series
- Real example: Dropbox to SharePoint migration
- How the secure Klara migration platform works
- Where the same approach can be used for other business systems
Talk to us
Planning a SYSPRO to Zoho, Sage, or other mid-market ERP data migration into Zoho One? Book an architecture session with Barberry Labs. We will assess source access, mappings, the minimum MCP permission scope and the customer approvals required for a controlled migration.