Taking over a stalled Zoho Creator app

Someone in the business built it, usually alongside Zoho CRM or Zoho Books, and it worked. Forms for the jobs, reports for the office, a few Deluge scripts to move things between them. Then it grew. The scripts multiplied and started to depend on each other. A report that was quick with a thousand records isn't with a hundred thousand. Each new person who needs to use it is another licence. Customers were promised a portal, which is another licence tier. The person who wrote the Deluge left, and the scripts are theirs.

None of that is a failure of Zoho Creator. It's a tool for building small applications quickly inside the Zoho ecosystem, and the trouble starts when a small application becomes the system.

• The structure and the logic, readable. The application exports as a .ds file: every form, field, report, page, schedule and Deluge script. It runs nowhere but Zoho, but it's a full description of what the app does and it's the specification for whatever comes next.
• The data. A backup, on the Professional edition and above, bundles the .ds file with a CSV per form. Records are also reachable through Zoho Creator's REST API, which is how a rebuild keeps both systems in step during the move.
• Attachments and files, through the same backup and API.
• The connections. What the app reads from CRM, Books or anything outside Zoho, which the scripts spell out.

Fix it in place when the app is small, close to the rest of Zoho, and stalled by something the platform can solve: a script rewritten, a report restructured, a schedule that fails quietly made to fail loudly. Zoho Creator is good at what it's good at, and we'll say so.

Rebuild on technology you own when the app has become the system. Performance that doesn't recover, a per-user bill that grows with the business, customers or suppliers who need access, integrations that Deluge can't reach, or rules the platform can't express. The rebuild starts from the .ds file as a specification, keeps the data, and runs alongside the Zoho app until each process has proven itself.

Often both. Stabilise it in place so it stops hurting, then move the processes that outgrew it. The general keep, finish or replace reasoning applies, and the assessment makes the call from the export and the data.

1. Export the application and take a backup, so its definition and its data exist somewhere you control, dated.
2. Read it. The assessment: every form, every report, every Deluge script and what it calls, every schedule, every connection to the rest of Zoho, and the licences each part needs.
3. Read the data. How many records, how clean, and how it comes out.
4. Decide, from evidence, per process: fix in place, or rebuild.
5. Rebuild alongside, where that's the answer. The new system runs in staging on the migrated data, checked by the people who use it, reconciled, then switched process by process. The Zoho app stays until the last one has moved.
6. Or fix in place, priced as its own stage, with the same test-then-live discipline.

It comes out of Zoho once as CSV, checked, and never meets a change until the change has proven itself somewhere else. The migration is tested against a copy in a test environment, then run in staging with every form and record count reconciled, before anything connects to live. Where the app shares data with Zoho CRM or Books, that link is rebuilt on Zoho's APIs so the two keep agreeing.

The assessment is from £395 + VAT, sized on a free one-hour consultation, with an exact price before you commit. For a Zoho Creator app it reads the export, the scripts and the data, and prices fixing in place and rebuilding as fixed numbers, alongside what the current licensing costs a year. What drives the price and the payment terms each have a page.

Read the export before deciding anything, and be willing to say the platform is fine. Marc Allington builds the web and .NET systems that apps move to when they outgrow a builder, and reads Deluge as one more scripting language. Everything we build runs on open technology in your own accounts, with full source code and ownership transferring to you on final payment, and no per-user licence.