NetSuite Customization Cleanup Staffing for Dead Scripts, SuiteScript 1.0 and Duplicate Workflows

Every NetSuite account past its fifth year has a script nobody can explain. It still runs. Somebody wrote it in a hurry for a customer who left in twenty nineteen, and nobody dares delete it. A health check finds those scripts. A cleanup removes them. KORE1 places the contract NetSuite developers who do the removing, billed hourly, with the rewriting done once and the paperwork left behind. Take one record. Ten customizations hang off the sales order. Three come out. Four get rewritten. Three stay exactly as they are. Look at two of the three coming out. Nothing on either of them is broken. They’re just still there, still firing, still getting tested every time NetSuite ships a release. That’s most of what a cleanup fixes. Scripts that outlived the field they read. Two workflows doing one job. Code on a SuiteScript version Oracle is retiring.

Every customization gets one of three verdicts. Oracle’s own transition guide for SuiteScript two point one asks for the same call on each legacy script. Update it, test it, or retire it when it’s inactive, obsolete or duplicated. Retire it when nothing it reads still exists, or a second script does its job. Rewrite it when somebody relies on it but it’s on the old version or runs slow. Leave it when it works and somebody owns it. Retiring isn’t deleting. Switch the deployment off, wait for one full month-end close to see whether anybody notices, and only then delete it. Leaving a script alone still means writing down what it does and how to turn it off. Then the work goes out in small batches, so when something breaks you know which batch did it.

So what does a cleanup cost? Hours times the hourly rate, seat by seat. KORE1-placed ERP and NetSuite consultants bill seventy-three to a hundred and twenty-three dollars an hour, median ninety-one. Software engineers bill ninety-one to a hundred and twenty, median a hundred and five. Senior software engineers bill ninety-one to a hundred and thirty-eight, median a hundred and twenty. Those are bill rates from the KORE1 Contract Rate Index for the fourth quarter of twenty twenty-six. The samples are small, fifteen, sixteen and seven placements, and the index has no NetSuite-only developer cell, so these are the closest rows. Three months at forty hours a week, at those median rates. The functional consultant comes to forty-seven thousand two hundred dollars. The developer, fifty-four thousand six hundred. The senior developer who owns the migration, sixty-two thousand four hundred.

KORE1 bills a cleanup hourly, on time and materials. You direct the developer. We handle the payroll. You pay for the hours worked, with a weekly note that shows where they went. We prefer hourly. It’s really a staffing model. We do the hourly billing and you manage the person. A budget cap is optional. A not-to-exceed number becomes the ceiling for the work. It limits the spend. It doesn’t promise the list fits under it. Monday, the developer picks the next batch and you confirm it. Midweek, changes go to the sandbox first. Friday, a burn note lands with hours used, customizations closed and how much of the cap remains.

Oracle published the schedule, and it applies to every account. Legacy SuiteScript support is expected to be removed in NetSuite twenty twenty-eight point two. A rewrite isn’t a find and replace either, because old functions don’t always map to the new modules. Somebody has to read each script and decide what it was really for. In NetSuite twenty twenty-seven point one, SuiteScript one point oh gets critical fixes only. In twenty twenty-eight point one, it can’t be deployed in new accounts. By twenty twenty-eight point two, everything must be on two point one. The calendar isn’t the only cost. Every release tests every script, even the dead ones. Two workflows that set the same field don’t fail loudly. They leave the final value up to whichever one fires last. A client script from twenty sixteen runs on every line edit, and reps stop trusting the order screen. And when the one person who understands the quarter-end helper leaves, a one-hour fix becomes three weeks of archaeology.

You might be wondering whether you have to move off SuiteScript one point oh. Eventually, yes. Scripts you’re keeping need to be on two point one before then, and scripts nobody uses just need to go. And can you hire the developer when the cleanup ends? Yes. A KORE1 contractor can convert to your payroll with no conversion fee after ten forty hours of contract work. Direct hire is open too. Send your health check findings. A rough count of scripts and workflows is plenty, plus when you’d like to start and how many hours a week you can fund. We’ll tell you which ones we’d cut first, and who we’d put in the seat.