Insist on an assessment before a plan
Good modernization begins with understanding what you have: dependencies, data stores, traffic patterns, the parts that change often and the parts nobody dares touch. A partner who quotes a migration before reading your code is guessing.
Ask for a written assessment that ranks components by business value, risk and effort.
Avoid the big-bang rewrite
Rewriting everything at once is the classic way to run over budget. Prefer incremental approaches such as the strangler pattern, where new services take over one capability at a time behind the existing system, so the business keeps running and each step can be reversed.
Security, observability and cost control
Check how the partner handles identity, secrets, network segmentation and backups, and how they set up logging, metrics and alerts so you can see problems before customers do. Ask about cloud cost controls too, since a lift-and-shift can raise the bill if resources are not right-sized.
A scorecard for modernization partners
Score partners on assessment depth, migration strategy, ability to work incrementally, security and identity practice, observability, cost control and how they plan the cut-over. A partner who explains how each step can be reversed deserves extra credit.
Modernization partner comparison at a glance
| What to check | A strong answer | A warning sign |
|---|---|---|
| Assessment | Written ranking of components by value, risk and effort | Quote given before reading the code |
| Strategy | Incremental migration using the strangler pattern | Full rewrite on day one |
| Rollback | Each step can be reversed | No rollback plan |
| Security | Identity, secrets, segmentation and backups planned early | Security reviewed after go-live |
| Cost control | Right-sizing and spend monitoring included | Lift-and-shift with no redesign |
Questions to ask in the first call
Ask how they would find hidden dependencies, which component they would move first and why, how data is migrated without downtime and what the rollback plan is. Ask how they prevent the cloud bill from rising after migration.
- Ask how they find hidden dependencies.
- Ask which component moves first and why.
- Ask how data is migrated without downtime.
- Ask what the rollback plan is for each step.
- Ask how the cloud bill is kept from rising after migration.
Phases of modernization
A reliable sequence is assessment and ranking, a target architecture, a pilot migration of one low-risk component, an incremental move of further capabilities, data migration and cut-over, then optimization of performance and cost. Database design and migration planning belong in the early phases, not at the end.
Mistakes buyers make
Mistakes include rewriting everything at once, lifting servers into the cloud without redesign and then paying more, ignoring the database, and leaving no budget for monitoring and training. A phased approach with measurable goals avoids most of them.
How NNT Software approaches modernization
We assess before we quote, move capabilities incrementally using the strangler pattern, and plan schema, index and data migrations early. We respond to every enquiry within 10 minutes, set up a meeting to understand your requirements, share a demo within 24 hours of that meeting, and then send a proposal that matches your budget.
We assess before we quote, and each migration step has a rollback plan and a measurable goal. A free 90-day defect warranty follows go-live, with a support plan available afterwards.
Example scenario: moving a legacy order system step by step
Illustrative scenario, not a client case: a company runs order processing on an ageing monolith in a data centre and wants to move to the cloud without a long freeze on new features. A careful partner begins with an assessment of dependencies, data volumes and risky integrations, and only then proposes an order of work.
Instead of a big-bang rewrite, one capability, such as pricing or notifications, is moved behind an API and run in parallel until its results match the old system. Each step has a rollback plan and a measurable goal, such as response time or monthly infrastructure cost, and the data migration is rehearsed several times before the final cut-over.
Red flags to walk away from
Be cautious of a partner who proposes rewriting the whole application at once, or who moves servers to the cloud unchanged and calls it modernization. Both tend to raise cost without improving the system.
Also question any plan that leaves the database for last. Schema, indexes and data migration shape every other step, so they belong in the first phase.
Budget and team
NNT Software’s rates are US$15–40 per hour. The final cost and timeline depend on the size of the system, the migration approach and the team members assigned, and are fixed only after the assessment confirms your requirements and budget.
Sources and further reading
More buyer guides
How NNT Software delivers projects like this
- Discovery — workshops, requirements and a written scope with a fixed estimate within days.
- Design — user flows, a clickable prototype and an architecture review before coding starts.
- Build — two-week sprints with demos, a shared backlog and code in your own repository.
- Test — dedicated QA, automated regression tests, performance and security checks.
- Launch — zero-downtime deployment, monitoring and user training.
- Support — SLA-backed maintenance and continuous improvement after go-live.