The enterprise platform is the most expensive thing your business rents.

It depends on how much of the platform you actually use. Companies running a handful of standard objects and a lot of workarounds are usually the easiest to replace, and the most relieved afterward. If you're deep into a platform-specific ecosystem, with dozens of managed packages and an in-house admin team, that's a much bigger conversation, and sometimes the answer is to stay and fix the configuration. We'll tell you which one you are on the call.

More than the license, and the gap surprises people. We don't quote those figures from memory. They're on a separate page covering average Salesforce and NetSuite implementation cost and timeline by company headcount, with every source cited and the thin spots marked as thin.

No, and it's a common call. Stopping a bad implementation early is cheaper than finishing it. We can look at what's been built, what the remaining spend buys you, and whether the honest move is to finish, renegotiate the scope, or rebuild the part that matters around your process.

Almost never. The piece causing the most pain gets replaced first while the rest keeps running, with a sync between the two. Each remaining module is then its own decision, and it doesn't get made until the first one has settled and people trust it.

Both are real work and we treat them that way. These platforms export and they have APIs, so records, history, attachments and the connections to your other systems get mapped field by field, then verified against the old system. Nobody switches anything off before that check passes. Running both side by side for a while is normal, and it's healthy.

Where the ecosystem is the product. If your industry has mature managed packages that encode regulation you'd otherwise build and maintain yourself, that's real value and it's expensive to reproduce. Same goes for a company whose auditors, insurers, or largest customers expect a named platform, and for one with a capable in-house admin team who've configured it well and aren't fighting it. NetSuite in particular earns its place in multi-entity, multi-currency operations with consolidated financials, which is genuinely hard to build from nothing. We say so on calls.

You take on responsibility you were renting. The vendor was doing real work for that money. It hosted the thing, shipped the upgrades, kept a compliance posture you could point an auditor at, and answered the support line. A custom system moves all of that to you and to whoever supports it. That's a good trade when the platform never fit and a poor one when it did. There's a hiring argument too. You can recruit a Salesforce administrator, and you can't recruit for "our own system." We answer that with code written to be read and accounts in your name. Pretending the question is unfair would help nobody.

No, and it matters that we say so. That's a different relationship from the one we had with Smartsheet, monday.com, Wrike and Zoho, where there were real partner programs that we later canceled. On these three we never had a badge to give up. What we have is integration work with Salesforce and HubSpot, and that's the claim we make.

Your own contract decides, so read the termination and data-return clauses before you give notice. Enterprise agreements typically define a limited window after termination during which you can retrieve your data, and once that window closes the vendor is under no obligation to keep any of it. Start the export check early and you avoid the whole problem. Finding this out in your last month is where rushed migrations come from.

They get rebuilt, and you want that in the plan up front. Reports and dashboards don't export from any of these platforms in a form another system can read, so the work is writing down what each one means before it disappears. That exercise usually turns up several reports nobody has opened in a year, and one report whose definition three departments disagree about. Both are worth knowing whether or not you migrate.