Top 10 Salesforce Implementation Rescue Partners in 2026: Who Can Fix a Failed Salesforce Project?
- Salesforce Implementation
Your Salesforce project is already in trouble. Maybe it stalled before go-live and the partner stopped returning calls. Maybe it’s live, but reps quietly went back to spreadsheets months ago. Maybe every new Flow breaks something that used to work, and nobody on your team fully understands why anymore.
Whatever shape the problem takes, the urgent question is who has genuinely fixed this kind of Salesforce failure before and whether your implementation needs targeted repair, a partial rebuild, or a fresh implementation.
That’s what this guide answers. Ten firms made the list, each with real, checkable rescue evidence behind them, matched to the kind of failure they’re actually built to fix.
TL;DR
Ten firms made this list after being evaluated specifically on rescue and remediation evidence, not general Salesforce implementation experience relabeled as recovery expertise. The list spans firms specializing in architecture remediation, data recovery, industry-specific rescues, and full partner-transition support.
Most Salesforce partner rankings reward size and certification count, which tells you almost nothing about whether a firm has ever diagnosed and fixed a genuinely broken implementation. A large, well-known consultancy with no visible rescue evidence isn’t automatically safer than a smaller firm with a documented failed-project takeover.
Start by figuring out whether your situation actually needs a rescue, a partial rebuild, or a full reimplementation, since that determines the kind of partner you need far more than company size does. Then match the specific failure you have, stalled delivery, broken data, architecture debt, abandoned adoption, to a firm with evidence of fixing that specific thing.
What Counts as a Failed Salesforce Implementation?
“Failed” covers more ground than most people assume, and the label matters because different failures need different fixes.
A stalled implementation never reached go-live; scope crept, the timeline collapsed, or the partner disengaged mid-project. A system that’s technically live but operationally failing launched on schedule, but reports can’t be trusted, workflows don’t match how the business actually operates, or basic processes require manual workarounds. Adoption failure means the platform works as built, but users quietly abandoned it for spreadsheets or the old system. Architecture failure shows up as a tangle of Flows, triggers, and customizations that nobody fully understands anymore, where every new change risks breaking something unrelated. Data failure means the numbers can’t be trusted, duplicate records, broken field mappings, incomplete migrations. And integration failure means the connections to your ERP, billing system, or other platforms break intermittently or never worked cleanly at all.
Most real failures are a combination of two or three of these, which is exactly why the diagnostic step matters more than the fix itself.
Rescue, Partial Rebuild, or Reimplement?
This decision comes before choosing a partner, and getting it wrong wastes both time and money in opposite directions.
Rescue fits when the foundation is sound and specific pieces are broken. The data model makes sense, the core architecture holds up, but a handful of workflows, integrations, or configuration choices need real repair. This is the least disruptive and fastest path when it’s the right call.
Partial rebuild fits when some components are genuinely solid and worth keeping, but major layers need to be replaced. Maybe the data model is fine but the automation layer has to be rebuilt from scratch, or the core CRM works but a critical integration needs a full re-architecture rather than a patch.
Reimplementation fits when the underlying architecture, data model, or process design is fundamentally wrong for the business, not broken in a few places, wrong at the foundation. This is the least common diagnosis and the most expensive path, and a credible rescue partner should never default to it without first proving the lighter options won’t work.
Salesforce’s own Well-Architected framework frames a healthy implementation around being trusted, easy, and adaptable, covering technical debt, data integrity, governance, and user engagement. That’s a more useful lens for this decision than a generic industry failure statistic, since it tells you specifically what to check before deciding how deep the fix needs to go.
Our Salesforce implementation services page walks through this same rescue-versus-reimplementation distinction in more detail, if you’re trying to make this call before you’ve even shortlisted a partner.
How We Selected the 10 Salesforce Implementation Rescue Partners
We started with roughly 14 candidates and verified each one against rescue-specific evidence before including it, not general Salesforce implementation credentials.
Named rescue projects and recovery case studies carried the most weight, followed by demonstrated architecture and remediation depth, data and integration recovery capability, a real diagnostic or takeover methodology, governance and testing rigor, and post-rescue support. Generic certifications and company size carried comparatively little weight, since neither tells you whether a firm has ever actually diagnosed and fixed a broken implementation.
One disclosure worth stating directly: VALiNTRY360 publishes this comparison and is included in the evaluation below. We applied the same evidence standard to our own listing that we applied to every other firm on this page.
Top 10 Salesforce Implementation Rescue Partners in 2026
Firm | Best for | Rescue evidence | Architecture depth | Data/integration recovery | Post-rescue support |
Advayan | Existing-org stabilization, troubleshooting, and implementation recovery | Implementation reviews, system health checks, troubleshooting, and optimization | High | High | Strong |
Xillentech | Architecture and technical-debt remediation | Confirmed “Generalist SI failed” takeover practice | Very high | High | Moderate |
HyphenX | Existing-org diagnosis, architecture cleanup, and implementation improvement | Org health assessment, gap analysis, optimization, and system-fix consulting | Moderate to high | High | Strong |
Coalescence | Salesforce plus Certinia/professional-services environments | AppExchange-listed Project Rescue offering | Moderate to high | Moderate | Moderate |
M&S Consulting | Mid-project turnaround for established organizations | Named implementation-rescue case | High | Moderate | Strong |
LOVALTO | Senior-led boutique rescue for financial services | Stated implementation-recovery focus | High | Moderate | Moderate |
Metadologie | Org cleanup across retail, nonprofit, and healthcare | General remediation and integration work | Moderate | Moderate | Moderate |
Green Irony | Preparing an unstable org for AI/agent readiness | Stated org optimization and cleanup focus | Moderate to high | Moderate | Moderate |
DX Foundation | Cross-system optimization and data-foundation repair | Stated cross-system remediation focus | Moderate | Moderate to high | Light to moderate |
VALiNTRY360 | Multi-problem recovery across data, adoption, and process | Documented audit and re-implementation service | Moderate to high | Moderate to high | Managed services with monitoring |
Advayan
Best for: Organizations with an existing Salesforce environment that needs stabilization across configuration, integrations, workflows, data, performance, or ongoing platform support.
Why they made the list: Advayan combines Salesforce implementation services with post-implementation support, system reviews, troubleshooting, release management, and continuous optimization. Its support process begins with a detailed review of the existing Salesforce implementation before moving into incident resolution and platform improvements.
Rescue evidence: Advayan’s published support process includes root-cause troubleshooting, fixing configuration errors, resolving integration failures and data-sync problems, addressing workflow interruptions, conducting system health checks, cleaning unused metadata, and optimizing validation rules. That gives it a practical foundation for stabilizing an implementation that is technically live but no longer operating reliably.
Where they’re strongest: Broad technical stabilization. Advayan covers implementation, integration troubleshooting, configuration fixes, workflow remediation, health monitoring, release management, performance optimization, and continuing support rather than concentrating on one narrow failure type.
Trade-off: Advayan’s public evidence is strongest around implementation, troubleshooting, maintenance, and ongoing optimization rather than a deeply documented named rescue case. Organizations dealing with a major failed implementation should ask for comparable recovery examples and confirm the exact team that would handle the turnaround.
Xillentech
Best for: Organizations whose implementation collapsed under architectural weight, too many customizations, brittle point-to-point integrations, or an org nobody fully understands anymore.
Why they made the list: A directly confirmed rescue practice: Xillentech states plainly that many of its clients arrive after a “Generalist SI” failed to deliver, and it begins every engagement with a comprehensive Org Health and Architecture Audit.
Rescue evidence: Beyond the audit practice, Xillentech uses API-led MuleSoft connectivity to replace brittle point-to-point integrations and works specifically in Salesforce Industry Clouds, including automotive, manufacturing, health, and public sector.
Where they’re strongest: Architecture and integration remediation, rebuilding the technical foundation rather than simply patching symptoms.
Trade-off: The depth here is architectural and technical. An organization whose core problem is adoption or process design rather than the underlying build may find a firm with stronger change-management capabilities a better fit.
HyphenX
Best for: Organizations with an existing Salesforce org suffering from process gaps, technical debt, data-quality problems, overlapping automation, unused functionality, or architecture that no longer reflects how the business operates.
Why they made the list: HyphenX explicitly includes existing-org assessment and Salesforce optimization in its consulting methodology. Its process reviews current configuration, workflows, automation logic, data quality, usage patterns, unused features, and technical debt before building a roadmap for improvements.
Rescue evidence: HyphenX’s published consulting process includes business discovery, existing-environment audits, architecture and data-model planning, phased implementation, adoption design, and post-launch optimization. Its current services also describe identifying Salesforce gaps and delivering practical fixes rather than layering new functionality onto unresolved problems.
Where they’re strongest: Diagnosis and restructuring. HyphenX connects Salesforce cleanup with process, automation, data, integration, architecture, and adoption decisions, making it useful when an organization needs to understand what is wrong before deciding what to repair, simplify, or rebuild.
Trade-off: HyphenX publicly documents a strong assessment, optimization, implementation, and system-improvement approach, but its available material does not show the same depth of named failed-project rescue cases as some dedicated recovery specialists. Buyers facing an emergency partner takeover should ask for directly comparable rescue references.
Coalescence
Best for: Organizations running Salesforce alongside Certinia, formerly FinancialForce, or other professional-services-focused ISV solutions where the implementation stalled or underdelivered.
Why they made the list: Coalescence’s AppExchange listing specifically names Project Rescue as an offering, positioned around implementations that stall, underdeliver, or lose stakeholder confidence.
Rescue evidence: The named Project Rescue service, combined with depth across Salesforce, Certinia, MuleSoft, and DevOps tooling such as Flosum and Gearset, suggests useful capability for professional-services-heavy environments.
Where they’re strongest: The Salesforce-plus-Certinia combination is a narrower, less commonly covered niche than general CRM rescue work.
Trade-off: That specialization is most useful for organizations actually running Certinia or similar professional-services tooling. A standard Sales or Service Cloud rescue may not require this specific depth.
M&S Consulting
Best for: Established mid-size to large organizations needing a documented, structured turnaround rather than emergency triage.
Why they made the list: A published, named implementation-rescue case study involving a national manufacturing and services organization, backed by a substantial operating history.
Rescue evidence: The named turnaround case, paired with a long delivery record, indicates experience managing recovery engagements rather than treating remediation as a one-off service.
Where they’re strongest: Structured, methodical delivery for organizations that want process rigor during an already stressful recovery.
Trade-off: A structured, established firm can move at a more deliberate pace than a smaller specialist. If the situation requires emergency stabilization, confirm mobilization timelines directly.
LOVALTO
Best for: Financial services organizations wanting senior-level architects involved in a rescue rather than a larger, more junior-staffed delivery team.
Why they made the list: LOVALTO positions itself around senior Salesforce architecture for financial services, with stated implementation-recovery capability for stalled or struggling post-go-live projects.
Rescue evidence: The firm’s stated focus on root-cause analysis and remediation for struggling implementations is specific, though the public evidence leans more heavily on positioning than independently detailed named rescue cases.
Where they’re strongest: Senior-level boutique delivery, particularly when the organization specifically wants architects closely involved in the recovery.
Trade-off: A boutique model typically means less bench depth for a large, multi-workstream rescue than a larger delivery organization can provide.
Metadologie
Best for: Organizations across retail, nonprofit, healthcare, or high-tech needing general cleanup and integration repair rather than a highly specialized architectural rescue.
Why they made the list: An established Salesforce partner with a substantial delivery record and integration experience across commonly used third-party business systems.
Rescue evidence: Metadologie’s evidence leans toward general implementation, customization, and integration work rather than a specifically named rescue methodology or case study. It is better treated as a broad remediation option than a specialized crisis-response firm.
Where they’re strongest: Practical integration and automation cleanup across common business systems.
Trade-off: Organizations facing a complex architectural failure may prefer a firm with a more explicitly documented rescue or architecture-remediation methodology.
Green Irony
Best for: Organizations preparing an unstable or messy Salesforce org for AI and agent readiness as part of the recovery.
Why they made the list: Green Irony positions its Salesforce consulting practice around improving orgs for AI agents, cleaner data, and stronger adoption, which can be relevant when the failed implementation includes data-quality or architecture-readiness problems.
Rescue evidence: The firm’s stated focus on org optimization and cleanup supports remediation work, although the evidence is more about current capability than a named, independently documented rescue case.
Where they’re strongest: Pairing data and architecture cleanup with forward-looking AI readiness, particularly when Agentforce is part of the organization’s longer-term roadmap.
Trade-off: If AI readiness is not part of the recovery goal, this specialization matters less and other firms may present stronger rescue-specific evidence.
DX Foundation
Best for: Organizations whose core failure is data fragmentation across multiple Salesforce clouds or connected systems.
Why they made the list: DX Foundation’s stated focus on cross-system optimization and coherent data foundations across Salesforce clouds addresses a common source of implementation problems.
Rescue evidence: The firm’s positioning centers on data-foundation and cross-system remediation rather than a specifically named rescue service, making it better suited to data-centric recovery than emergency project takeover.
Where they’re strongest: Data architecture across multiple Salesforce clouds and connected systems rather than a narrow single-cloud repair.
Trade-off: For a rescue primarily caused by adoption failure or process breakdown rather than data architecture, this specialization may be less important.
VALiNTRY360
Best for: Organizations with a multi-problem recovery involving some combination of data quality, adoption, workflow, security, and integration issues, where an audit is needed before deciding what should be repaired or rebuilt.
Why they made the list: A documented service for failed or stalled Salesforce implementations covering org health and technical assessment, data quality and migration review, workflow and automation assessment, integration review, security and permissions, adoption and training gaps, backlog prioritization, and remediation planning.
Rescue evidence: The audit-first structure covers several common sources of Salesforce implementation failure together rather than assuming one technical issue explains the entire problem. A precise rescue timeline should still be confirmed for the specific engagement rather than assumed from broader Salesforce implementation timelines.
Where they’re strongest: Breadth. The assessment covers data, workflows, integrations, security, and adoption together, with managed services available when the organization needs ongoing platform support after stabilization.
Trade-off: That breadth is useful for a genuinely multi-problem recovery. An organization with one narrow, clearly diagnosed issue may not require a full multi-area assessment before remediation begins.
Which Rescue Partner Fits Your Salesforce Failure?
Ten firms with credible recovery or remediation capabilities still do not create a useful shortlist unless you can connect your specific problem to the type of expertise required. This matrix makes that comparison easier.
Your Salesforce problem looks like… | Rescue capability you need | Best-fit partners |
Implementation stalled before go-live | Project assessment, scope reset, and delivery recovery | M&S Consulting, HyphenX |
Salesforce went live but users abandoned it | Process redesign and adoption recovery | VALiNTRY360, M&S Consulting |
Too many Flows, triggers, and customizations | Architecture and technical-debt remediation | Xillentech, DX Foundation |
Reports cannot be trusted because data is broken | Data remediation and governance | DX Foundation, VALiNTRY360 |
ERP or API integrations keep failing | Integration architecture and remediation | Xillentech, Coalescence |
Existing Salesforce configuration and workflows are unstable | Configuration review, troubleshooting, and platform stabilization | Advayan, VALiNTRY360 |
Previous implementation partner disappeared | Implementation assessment, remediation planning, and partner transition | Advayan, Coalescence |
Nobody knows whether to repair or rebuild | Architecture and existing-org assessment | HyphenX, Xillentech |
Security and permissions are out of control | Security and governance remediation | Metadologie, VALiNTRY360 |
Org works today but every new change breaks something | Architecture, DevOps, and testing discipline | Xillentech, Coalescence |
A few firms appear more than once because their capabilities genuinely span several failure types. Xillentech and VALiNTRY360 cover multiple technical and operational recovery areas, while HyphenX brings an assessment-led approach across architecture, data, automation, integrations, and process alignment. Advayan fits situations where implementation problems have moved into stabilization, troubleshooting, remediation, and ongoing support. Firms with narrower specialization should still be evaluated where their specific expertise matches the root cause of the failed implementation.
What Should Happen in the First 30 Days of a Salesforce Rescue?
No two rescues run on an identical clock, but a disciplined takeover follows a recognizable shape, and knowing that shape gives you a benchmark to hold a new partner against.
Days 1 to 5 should focus on stabilizing the environment, freezing unnecessary production changes, and gathering evidence before remediation begins. The incoming team needs a clear view of the current system before deciding what is safe to change.
Days 5 to 10 cover the org, data, and integration audit, the technical inventory of what exists, what’s configured correctly, what’s duplicated, and what’s quietly failing. This is where a firm like Xillentech’s Org Health and Architecture Audit or VALiNTRY360’s technical audit process does its real work.
Days 10 to 15 move into root-cause analysis. The rescue team should establish why each major failure occurred so the remediation plan addresses the underlying cause rather than patching symptoms that could surface again later.
Days 15 to 20 are where the salvage-versus-rebuild decisions take shape, based on the architecture, data, integration, and process findings gathered during the earlier assessment work.
Days 20 to 30 should produce a prioritized stabilization plan that identifies what needs immediate remediation, what can wait, which components should be preserved, and what the realistic delivery sequence looks like from that point forward.
Not every rescue will fit neatly into this 30-day model. A large multi-cloud failure can take much longer to diagnose than a single broken integration. The important signal is the sequence: stabilization, evidence gathering, root-cause analysis, salvage decisions, and then a prioritized recovery plan. A partner proposing a full rebuild before completing comparable diagnostic work is making that recommendation too early.
What Should a Salesforce Rescue Assessment Include?
A real assessment goes well past “let’s look at your Salesforce org.” It should cover architecture and technical debt, the Flows, triggers, and Apex that make up the current build and how much of it is sound versus fragile.It should cover data quality, duplication, failed mappings, incomplete migrations, and whether the records driving your reports can actually be trusted. If migration issues are part of the failure, review the scope of the problem against a structured Salesforce data migration .
It should cover integrations, including every connection to an ERP, billing system, or third-party platform, which integrations are failing, and whether the underlying architecture needs repair. Our Salesforce integration services page shows the integration areas that should be reviewed when connected systems are part of the failure.
It should cover permissions and security, since a messy implementation often has messy access controls layered on top of it. It should cover reports, release management, and testing practices, whether changes go through any real process or just get pushed straight to production. It should cover user adoption, not just whether the system works, but whether people are actually using it. And it should cover documentation, the current backlog, and, critically, the business outcomes the implementation was originally supposed to deliver, since a technically sound rescue that still misses the original business goal isn’t actually a fix.
Our Salesforce Health Check service is built around exactly this scope, instability, security risk, data quality, inefficiency, and adoption issues, if you want to see what a structured version of this assessment looks like before you commit to any specific rescue partner.
How to Change Salesforce Implementation Partners Without Making the Project Worse
A partner transition is its own risk, separate from whatever caused the original failure, and it’s worth handling deliberately.
Start with documentation handover: architecture decisions, configuration choices, and any design rationale the outgoing partner can provide. Confirm credential and access control immediately, who has admin rights, and revoke access that shouldn’t persist once the relationship ends. Establish sandbox ownership clearly, since a rescue team needs a safe place to work that isn’t production. Get source control and deployment history if any exists, since understanding what changed and when is often half the diagnostic work. Get a full list of open defects and known issues rather than discovering them one at a time. Gather integration credentials and documentation for every connected system. Request data mappings from any prior migration work. Review the original statement of work boundaries, so the incoming partner understands what was originally promised versus what was actually delivered. And insist on real knowledge transfer, direct conversations with whoever built the original system where possible, not just a document dump.
Skipping this step is one of the most common ways a partner switch adds a second layer of chaos on top of the first.
Red Flags in a Salesforce Rescue Partner
A handful of behaviors are worth treating as disqualifying, not just mildly concerning. A partner who starts changing production before completing a real audit is skipping the step that tells them what’s actually safe to touch. A partner who promises a full rebuild before finishing that audit is selling you a solution before diagnosing the problem. A partner who spends the sales conversation blaming everything on the previous implementer, without demonstrating they understand your specific failure, is performing confidence rather than earning it. A partner who can’t clearly explain what they plan to preserve from the existing implementation likely hasn’t looked closely enough to know. A partner who doesn’t ask to see your actual data before proposing a fix is guessing. A partner with no rollback strategy is one bad deployment away from making your situation worse, not better. A partner who can’t separate urgent stabilization work from longer-term optimization work will likely blur the two in a way that delays real fixes. And a partner who treats every existing customization as automatic technical debt to be ripped out, rather than evaluating each one individually, is applying a philosophy instead of doing the actual diagnostic work.
Any one of these is worth a direct follow-up question. More than one or two should meaningfully lower your confidence in the pitch.
Where VALiNTRY360 Fits
VALiNTRY360 is included in the ten above and was evaluated against the same evidence standard applied to every other firm in this comparison.
Where we tend to be best suited to multi-area recovery is where data quality, workflow design, integrations, permissions, reporting, and adoption need to be assessed together before remediation begins. Ongoing Salesforce managed services can then support the org after stabilization through monitoring, maintenance, optimization, and continued administration. A narrow, isolated technical problem may be better served by a specialist with deeper evidence in that exact area.
The Bottom Line
Choose the rescue partner based on the Salesforce failure you actually need fixed rather than the overall size of the firm’s Salesforce practice.
Start with the diagnosis. Determine whether the implementation needs targeted repair, a partial rebuild, or a full reimplementation. Then match the underlying failure, whether architecture, data, integrations, adoption, security, or industry-specific configuration, to a firm with documented evidence in that area. Use the Rescue Fit Matrix to narrow the shortlist and the red flags above to pressure-test each partner during the first conversation.
A failed implementation does not tell you how much needs to be rebuilt. A proper assessment should establish what can be preserved, what requires remediation, and whether the underlying foundation is still viable.
Frequently Asked Questions
How do I know if my Salesforce implementation needs a rescue or a full reimplementation?
Start with an independent audit rather than guessing. If the core data model and architecture are sound and specific pieces are broken, a rescue fits. If the foundation itself is wrong for how your business operates, reimplementation is likely the only real fix, but that diagnosis should come from evidence, not assumption.
How long does a typical Salesforce rescue project take?
It depends heavily on the scope of the failure and how many systems are involved. A single broken integration can be fixed in weeks; a multi-cloud architecture and data recovery can take several months. Ask any partner for a timeline based on your specific audit findings, not a generic range.
What’s the difference between a Salesforce health check and a rescue engagement?
A health check is diagnostic: it identifies what’s broken and why. A rescue engagement includes the actual remediation work, fixing the architecture, data, integrations, or adoption issues the health check uncovered. Many rescues start with a health check as the first phase.
Should I fire my current Salesforce partner before starting a rescue?
Not necessarily, and not immediately. Some rescues happen alongside the existing partner if the relationship is still workable. If you do switch partners, secure documentation, credentials, and access before ending the relationship, since losing that information mid-transition adds real risk.
Can a failed Salesforce implementation be fixed without losing existing data?
In most cases, yes, if handled carefully. A competent rescue partner audits existing data before making changes and identifies what’s salvageable versus what needs correction. Data loss typically happens when a rescue skips the audit step and moves straight into rebuilding.
What does it mean if my Salesforce org has too much technical debt?
It generally means the accumulated Flows, triggers, customizations, and workarounds have made the system fragile, where a small change in one area risks breaking something unrelated elsewhere. Salesforce’s own Well-Architected guidance treats reducing this kind of debt as central to a healthy, maintainable org.
Why did our Salesforce implementation fail even though we hired a certified partner?
Certification measures platform knowledge, not necessarily rescue or complex-project experience. A partner can be fully certified and still misjudge your specific business processes, data condition, or integration complexity. This is why rescue-specific evidence matters more than general certification when things go wrong.
What questions should I ask a potential rescue partner before hiring them?
Ask what they plan to preserve from your existing implementation, what their audit process looks like before any changes are made, whether they have a rollback strategy, and for a specific example of a comparable rescue they’ve completed. Vague or reassuring-but-generic answers are a warning sign.
Is it normal for a Salesforce implementation to need a rescue?
Salesforce rescue services exist because stalled projects, weak architecture, data problems, poor adoption, and partner transitions all occur in real implementations. The important question is the cause of your specific failure and whether the existing foundation is still worth preserving.
How much does a Salesforce rescue typically cost compared to reimplementation?
A rescue is generally less expensive than a full reimplementation, since it preserves and repairs existing work rather than rebuilding from scratch. The exact cost depends on how much of the original implementation is salvageable, which is precisely what the initial audit is meant to determine.
Can a Salesforce rescue partner also help with ongoing support after the fix?
Many can, though not all offer it as a structured, named service. If ongoing support matters to you, ask specifically whether post-rescue monitoring or managed services are included, rather than assuming every rescue engagement automatically includes them.
What’s the biggest mistake companies make when hiring a Salesforce rescue partner?
Choosing a partner based on reputation or size alone, without confirming they have specific evidence of fixing a comparable failure. A large, well-known firm without visible rescue experience isn’t automatically a safer choice than a smaller firm with a documented, relevant track record.
Should I trust a rescue partner who wants to start rebuilding immediately?
Be cautious. A credible rescue partner completes a real audit before proposing significant changes, since rebuilding before understanding what’s actually broken risks losing what still works. A partner skipping straight to “let’s rebuild” hasn’t yet earned that recommendation.
Do I need a Salesforce-certified partner specifically, or can a general IT consultancy handle a rescue?
Salesforce-specific expertise matters significantly here, since rescue work requires deep platform knowledge to distinguish a configuration problem from an architecture problem from a data problem. A general IT consultancy without dedicated Salesforce depth is a meaningfully higher-risk choice for this kind of work.
What happens if my rescue partner discovers the implementation needs a full reimplementation after all?
A trustworthy partner will tell you this directly, even if it means a smaller initial engagement than a full reimplementation would have been. This is exactly why starting with an audit rather than a fixed rebuild commitment matters, it lets the evidence determine the path rather than locking you into one before the diagnosis is complete.