Failed CRM implementation: fix it or switch partners

When a CRM is live and the team still works from spreadsheets, you are looking at a failed CRM implementation, and you have three options: repair it in place, bring in a second partner, or restart on another platform. Four checks sort out which cause you have: adoption, data quality, process fit and partner access. When the data model fits, adoption, data cleanup and access problems stay on the platform you already licensed. Nucleus Research rechecked 63 CRM case studies in August 2023 and reported that average return had fallen 37 percent, from USD 4.90 to USD 3.10 per dollar spent (Nucleus Research).

An unused CRM still bills every month, which makes the repair decision worth an afternoon of diagnosis. Below you will find four checks to run this week, a decision tree for the three branches, the contents of a proper rescue assessment, and the access and data steps to finish before your current partner goes quiet. Read the 90-day cancellation section before you cancel anything or change any access.

What the published CRM return numbers show

Nucleus Research has tracked CRM return per dollar for more than a decade. Its 2011 news release reported an average return of USD 5.60 per dollar spent. A page Nucleus still publishes puts the figure at USD 8.71 per dollar. In August 2023, Nucleus reexamined 63 CRM ROI case studies from the prior decade and reported that the average had fallen 37 percent, from USD 4.90 to USD 3.10. Both the USD 8.71 page and the 2023 note are live on Nucleus's site, so when one number goes into a budget conversation, use USD 3.10 and say it comes from the 2023 reanalysis of 63 cases.

Odoo publishes an implementation claim of its own: a "98% implementation success rate, vs 65% without success pack", which Odoo marks as self-reported. Read it as a vendor's argument for buying implementation hours, then measure your own system the same way after any rescue: weekly active sellers against licensed seats.

For two companies of the same size on the same plan, the license invoice is nearly identical. Return separates on what happens after go-live, and usage is what the four diagnostics below measure.

Four diagnostics that tell you what failed

Run these in a week, with data you already have. Each check ends in a finding, and the four findings together pick the branch of the decision tree in the next section.

Adoption: licensed seats against weekly sellers

Pull two numbers from admin: licensed users, and sellers who logged in during the last full week. In a working rollout the second number sits close to the first. When it drifts, reps keep side spreadsheets, opportunities skip stages, and required fields get any text that silences the validation.

A comment on a small-business thread describes the end state: "the CRM gets abandoned and everyone goes back to their old spreadsheets and email threads" (Reddit). The same thread names two causes you can act on this month: "Training gets skipped or rushed" (Reddit), and field updates that wait for a desk, because "If updating the CRM requires going back to a desktop computer, it won't happen consistently." (Reddit)

Data quality: would you trust a pipeline report today

Count duplicate accounts, accounts with no activity in six months, and opportunities with no close date. Comments in the same thread warn that "The CRM becomes cluttered with bad data" and that "Garbage in, garbage out applies heavily to CRM systems." (Reddit). If your forecast meeting opens with apologies for the numbers, the failure sits in the data layer, and it will follow you to a new platform unless someone cleans it first. Migration moves bad records at the same speed as good ones.

Process fit: does the data model match how you sell

The test is whether the system can represent your stages, products, quotes and approvals without custom code fighting the process. Symptoms of a mismatch: the real pipeline lives in a spreadsheet because the stages do not exist in the CRM, managers export to Excel to see anything, and every process change becomes a paid change request. This finding weighs heaviest in the decision tree, because a broken data model is the one failure a retraining program cannot fix.

Partner access: who holds the keys and who answers

Four signals: nobody inside the company owns the system after go-live; the partner holds the only Global admin account or the only Odoo.sh access; customizations sit in solutions only the partner can export; response times have slipped from days to weeks. A long thread on r/CRM describes the pattern: "CRM projects usually start failing long before the software becomes the issue" (Reddit). Two or more of these signals put the partner question on the table next to the platform question.

Repair in place, bring in a second partner, or restart

The diagnostics sort you into one of three branches.

Repair in place when the platform fits and the gap is usage

If the data model matches how you sell, your team holds admin access and the core screens work, the failure is usage and cleanup. The repair is a management project: name an internal owner with allocated hours, retrain by role against the real pipeline, merge duplicate accounts, and cut the field list down to what managers read in reviews. Our CRM adoption guide covers the in-place repair branch in detail.

Change partners when the platform fits and the work did not

If the platform fits but the statement of work was thin, the admin rights never moved to your team, or the adoption design never existed, a second partner can take the project over. Your Dynamics 365 licenses and data live in your own Microsoft tenant, so an incoming partner builds on what exists. On Odoo Online, the database backup downloads from the control center at any time; on Odoo.sh or on-premise, confirm the backup path with whoever runs that hosting before the handover. Ask each candidate for three things: a written plan that starts from your current solution inventory and security roles, a data-quality remediation step with a stated sample size, and admin control transferred to your team in the first week of the engagement. We take over projects on both platforms, and the assessment in the next section is how a handover starts.

Restart when the data model or the code cannot carry you

Two findings point here: the data model cannot represent your sales process even after configuration, or the customizations are undocumented and unmaintainable, so no second partner can safely own them. Price a restart with open eyes: a new platform brings new subscriptions, migration, retraining and a parallel-running period, and you still need to export the old system's history so pipeline reporting keeps its baseline. If your diagnostics point at inventory or order-to-cash integrations behind the CRM, the same decision runs one level up, and our failed ERP implementation rescue guide covers that larger case.

What a rescue assessment should include

An assessment turns the four diagnostics into a written recommendation, and it is the deliverable to demand before anyone quotes a rescue project. Eight areas cover it:

• Licenses and security roles: Seats by plan, unused seats, roles that grant too much or too little
• Environments and backups: Every environment listed, the backup retention in force, restore limits confirmed
• Solution inventory: Each customization, the solution or module that holds it, and who can export it
• Integrations: Every connection in and out, its owner, and what breaks when it fails
• Data quality: Duplicate and stale rates measured on a sample, with a remediation estimate
• Adoption by role: Weekly active sellers against licensed seats, team by team
• Project paper: The open statement of work, the change-request log, and what remains unpaid
• Recommendation: A written keep, repair or restart call with the reasoning behind it

The retention row has a published floor: Dataverse system backups are kept 7 days by default, and a production managed environment can be extended to 14, 21 or 28 days. No published duration or fee for this assessment was found, so put two asks to every bidder: price the assessment as its own line, and state duration, price and deliverable in writing. We run the assessment as a standalone first step, and the written recommendation ends it, whether you continue with us or take it to another firm. See our CRM services for how that engagement is structured.

What to secure from your current partner before you switch

Secure access and copies first, then change partners, then scope the repair. Reversing that order is how companies end up negotiating for data they already own.

• Admin control in your name: Confirm your team holds Global admin and Power Platform admin. Add your own admin first, and remove the partner's delegated access only after your admin sign-in works.
• A fresh backup inside the retention window: Have an admin trigger a backup and check the date of the newest restore point.
• A full data export: Excel exports for small sets and a scoped data migration for the rest, because Microsoft does not support downloading a copy of an online Dataverse database backup (Microsoft Learn). On Odoo Online, you can download a database backup at any time from the control center.
• Customization source: The solution inventory, the source code for custom modules, and the module list on Odoo.
• The ownership clause: The statement of work section on who owns configurations and code, filed with the change-request log.
• The privacy clock in Canada: If the CRM holds personal information about Canadians, PIPEDA requires access within 30 days of a request, with one 30-day extension in defined cases, and correction of inaccurate records. The duty applies even when a partner built the system.

On ownership, Microsoft's Trust Center states that you own your data and that Microsoft uses customer data only to provide the agreed services. Odoo's pricing page makes the same statement. The contract stack behind the service: Power Platform and Dynamics 365 online use is governed by the Microsoft Online Subscription Agreement or the Microsoft Customer Agreement, which incorporate the Product Terms and the Data Protection Addendum, and the current DPA is the May 2026 edition. Access and copies are what you control day to day, and the table above secures both.

Backup windows, restore limits and the 90-day cancellation clock

The retention numbers decide how fast you have to move. As of October 2026:

• Dataverse system backup retention, default: 7 days for production and nonproduction environments
• Extended retention on a production managed environment: 14, 21 or 28 days, set by a Power Platform admin, Global admin or Dynamics 365 admin
• Restore of a large environment: Up to 48 hours
• Restore prerequisites: At least 1 GB of free capacity, and a restore cannot be applied directly onto production, so switch to a sandbox first
• Downloading an online Dataverse database backup: Not supported; Excel exports for small sets and a data migration for larger moves
• Recovery of a recently deleted environment: 7 days, or up to 28 days for production environments with Dynamics 365 applications
• Data retention after subscription cancellation: 90 days in a limited-function account, then deletion within a further 90 days for in-scope services

Sources: Microsoft Learn's backup and restore documentation and Microsoft's data-management page, as of October 2026.

The last row changes decisions. Cancelling the subscription to stop the billing starts a 90-day extraction window, after which Microsoft disables the account and deletes customer data, including cached and backup copies, within a further 90 days for the online services in scope (Microsoft). If a restart is on the table, run the export and the new platform's migration in parallel while both systems are live. A default 7-day backup window also means last quarter's state survives only if someone extended retention or exported a copy.

What a rescue costs against a restart

Start from the invoice you pay either way. Assume 20 sellers on Dynamics 365 Sales Enterprise: at USD 105 per user per month, paid yearly, the tenant bills USD 2,100 per month at US list, or CAD 2,850 per month at the Canadian list of CAD 142.50 per user, plus applicable tax. That invoice runs through a rescue and through a restart, so the comparison that matters is the extra cost of each path.

A restart adds a second subscription on top of the one you keep paying until the export is done. Current list prices for the platforms in this article, as of October 2026:

• Dynamics 365 Sales Professional (List price: USD 65 · Basis: per user per month, paid yearly)
• Dynamics 365 Sales Enterprise (List price: USD 105 · Basis: per user per month, paid yearly)
• Dynamics 365 Sales Premium (List price: USD 150 · Basis: per user per month, paid yearly)
• Salesforce Starter Suite (List price: USD 25 · Basis: per user per month as displayed)
• Salesforce Pro Suite (List price: USD 100 · Basis: per user per month as displayed)
• Salesforce Core (List price: USD 195 · Basis: per user per month as displayed)
• Salesforce Advanced (List price: USD 395 · Basis: per user per month as displayed)
• Salesforce Max (List price: USD 550 · Basis: per user per month as displayed)
• Odoo Standard (List price: EUR 24.90 · Basis: per user per month, first 12 months for initial users; struck list EUR 31.10)
• Odoo Custom (List price: EUR 44.90 · Basis: per user per month, first 12 months; struck list EUR 56.90, Odoo.sh hosting extra)

Sources: Microsoft notes that displayed prices are informational and the checkout price can differ by currency and region, and the same Sales plans list at CAD 88.20, CAD 142.50 and CAD 203.50 in Canada plus applicable tax. Salesforce labels its pricing page informational and subject to change. Odoo's page renders in euros and lists Standard at EUR 24.90 and Custom at EUR 44.90 for the first 12 months, against struck lists of EUR 31.10 and EUR 56.90; Odoo states that implementation is not included in the subscription.

Odoo's packaged prices are the clearest public floor for a greenfield build, because Odoo sells Success Packs as implementation services: EUR 499 for a Starter pack of 4 consultant hours, EUR 2,635 for Basic at 25 hours, EUR 4,675 for Standard at 50 hours, EUR 8,415 for Custom at 100 hours and EUR 16,830 for Pro at 200 hours for new customers, and EUR 19,800 for the Pro pack for returning customers, all as of October 2026. In the estimator's example scope, Odoo says 80 percent of projects reach production in 200 hours or less (Odoo). Odoo's own guidance on who builds: companies under 50 employees usually implement with Success Packs, companies over 50 usually use a partner, and partners charge per day at rates the page does not publish, so ask every bidder for a day rate and an hour estimate.

When the repair quote and the restart quote land close together, the process-fit diagnostic breaks the tie. A sound data model tips the decision toward repair, since the expensive part already works. A model that cannot represent your sales process tips it toward restart, since repair would preserve the thing that broke.

How we run a CRM rescue at Flectic

Flectic implements Microsoft Dynamics 365 and Odoo for companies of about 20 to 100 people in the US and Canada, and a stalled CRM is a common reason companies first contact us. The sequence in this article is the sequence we work to: an assessment with a written keep, repair or restart recommendation, access and data secured under your team's control, then either a phased repair with a named internal owner or a managed handover with a second partner. We deliver Dynamics 365 Sales implementations and Odoo projects on the same phased method, the Flectic Accelerated Delivery Framework. If the diagnostics put you in the repair or second-partner branch, our CRM services page explains the assessment and the phased repair, and the first call goes best with your license count and your four diagnostic answers in hand.

How Flectic can help

Flectic sets up Dynamics 365 Sales for sales teams of 20 to 100 people in the US and Canada, with stage rules and quotes on the opportunity, so the pipeline is one you can forecast from. A fixed-price first phase delivers a working pipeline before you commit the full budget. If the CRM is live but the team still forecasts in spreadsheets, see Dynamics 365 Sales implementation, and we will scope the fix before any rebuild. Book a free discovery call with Flectic to compare repair, a second partner and a restart.

Sources

• CRM returns $3.10 per dollar spent, Nucleus Research, August 2023
• CRM pays back $8.71 for every dollar spent, Nucleus Research, September 2023
• CRM returns $5.60 for every dollar invested, Nucleus Research, 2011
• Data management at Microsoft, Microsoft, October 2026
• Microsoft Products and Services Data Protection Addendum, Microsoft, May 2026
• Dynamics 365 legal terms, Microsoft, October 2026
• Back up and restore environments, Microsoft Learn, October 2026
• Dynamics 365 Sales pricing (United States), Microsoft, October 2026
• Dynamics 365 Sales pricing (Canada), Microsoft, October 2026
• Salesforce Sales pricing, Salesforce, October 2026
• Odoo pricing, Odoo, October 2026
• Odoo Success Packs, Odoo, October 2026
• PIPEDA Fair Information Principle 9: Individual Access, Office of the Privacy Commissioner of Canada, August 2020
• Why CRM Implementation Fails for Most Small Businesses, Reddit, October 2026
• Is anyone else noticing that CRM projects usually start failing early, Reddit, October 2026