The manufacturing company had done everything right on paper. They had a signed contract with a Salesforce partner, an executive sponsor, a defined timeline, and a budget. Their go-live date came and went as planned. Salesforce was live.
But six months later, they were in trouble. Three different account naming formats coexisted in the system because no one had standardized data before migration. The integration with their ERP was pulling in pricing data that was eighteen months out of date. And the sales team — the people the whole project was meant to help — had quietly gone back to using their spreadsheets because nobody had trained them on the new workflows before launch.
Technically, the implementation was complete. Operationally, it had barely started.
This outcome is more common than any Salesforce partner wants to admit. Implementations fail not because of bad technology but because of the phases that got rushed, skipped, or scoped too narrowly. Here is what every Salesforce implementation actually requires - and where delays and failures most often originate.
Every Salesforce implementation begins with a discovery phase, and every delayed implementation has a discovery phase that was not taken seriously enough.
Discovery is where the implementation partner maps your current processes, identifies gaps, defines what Salesforce will and won't do in its first version, and documents the integrations and data migrations required. For organizations in manufacturing, distribution, or industrial sectors, this phase must explicitly scope the ERP environment — what data from SAP, PeopleSoft, or Oracle needs to flow into Salesforce, how it will be kept current, and who owns the integration from the business side.
The most expensive discovery mistakes are those of omission. An integration that was assumed to be simple — pulling customer master data from the ERP, for example — often turns out to require field mapping, data transformation, and ongoing sync logic that adds weeks to the project. Discovering this in Phase 3 is significantly more disruptive than discovering it in Phase 1.
A thorough discovery phase produces: a confirmed scope document, an agreed requirements list ranked by priority, an integration map showing every system that will connect to Salesforce, and a data migration assessment covering source system quality and volume.
Data migration is the most consistently underestimated part of a Salesforce implementation. Most project plans allocate time for the migration itself but not for the work that has to happen before it: assessing data quality, deduplicating records, standardizing formats, mapping legacy fields to Salesforce objects, and handling records that don't fit neatly into any Salesforce schema.
For companies moving from a legacy CRM, an ERP, or spreadsheets, the source data is almost always messier than expected. Accounts with duplicate entries. Contacts attached to the wrong accounts. Opportunities with missing stage dates. Open activities with no assigned owner.
Migrating this data without cleaning it first means importing problems into Salesforce that will take months to fix after go-live - exactly the situation the manufacturer in the introduction found themselves in.
Data migration planning should begin in parallel with configuration work, not after it. Minuscule's data migration practice includes source system assessment, field mapping documentation, migration scripts, and post-migration validation to confirm record counts and data integrity before go-live.
With discovery complete and data mapping underway, configuration work begins. This is where Salesforce is built to match your business processes: object configuration, page layouts, record types, automation rules, approval processes, reports, and dashboards.
For most organizations, at least one integration runs in parallel: connecting Salesforce to the ERP, the marketing automation platform, the customer service system, or the distributor portal. Minuscule's Salesforce integration services cover MuleSoft-based and API-native connections to SAP, PeopleSoft, Denodo, and other enterprise systems.
The key principle in this phase is to build for the MVP, not the ideal future state. Many implementations get delayed because the scope expands during development — new requirements are added, edge cases multiply, and the go-live date shifts to accommodate features that weren't in the original scope. A disciplined Phase 1 and a clear MVP definition are the best defenses against this.
UAT is where the business confirms that what was built matches what was agreed. It is not a technical QA phase — it is a business sign-off phase, and it requires time, access, and attention from the same users who will operate Salesforce after go-live.
This is where many timelines slip. UAT is scheduled for two weeks; stakeholders are too busy to participate; feedback comes in late; fixes require additional testing rounds; the go-live date moves.
The solution is not to compress UAT. It is to plan for it properly: block time on stakeholder calendars during discovery, define test scenarios in advance, and build buffer into the project plan for the inevitable UAT feedback cycle. According to Salesforce's implementation best practice guidance, UAT should be structured with defined entry criteria, test case documentation, and clear sign-off requirements.
Training should happen after UAT confirms the system is stable, not before. Reps trained on a system that subsequently changes will default to workarounds. Train close to go-live, using real scenarios from your actual business.
Go-live is not the end of the implementation — it is the beginning of the most critical period. The first thirty days after launch, often called hypercare, are when issues surface that no test environment could have predicted: edge cases in real data, user behavior patterns that differ from how workflows were configured, and integration errors that only appear under production load.
Organizations that plan for hypercare — with dedicated support resources available, a clear escalation path for issues, and a process for capturing post-go-live change requests — absorb these issues without disruption. Organizations that treat go-live as the finish line discover problems without any structure to address them.
Minuscule's managed services team provides post-go-live support that covers hypercare, ongoing administration, and Salesforce release management — so that the work done during the implementation is maintained and extended over time.
Salesforce implementation services typically cover discovery and requirements gathering, configuration and customization, data migration, system integration, user acceptance testing, training, and post-go-live support. The scope varies based on which Salesforce clouds are being deployed and what existing systems need to connect to the platform. A quality implementation partner will document exactly what is and isn't included in each phase before work begins.
A focused Sales Cloud or Service Cloud implementation for a mid-size organization typically runs across several months from kickoff to go-live, depending on integration complexity, data migration volume, and the number of custom configurations required. Implementations that scope ERP integrations, multi-cloud deployments, or large data migrations require additional time. Rushing any phase - particularly discovery or UAT - is the most common cause of go-live delays.
The most frequent causes of delays are: an incomplete discovery that misses integration or data migration requirements; scope changes during the build phase; UAT that starts too late or runs without adequate stakeholder participation; and data quality issues discovered only when migration work begins. Most delays are preventable with rigorous Phase 1 planning and a disciplined MVP scope. According to SalesforceBen's implementation guide, under-scoping and over-customization are the two leading causes of failed or delayed projects.
Yes - data quality is one of the most important and most overlooked inputs to a successful implementation. Migrating dirty data (duplicates, inconsistent formats, missing fields, orphaned records) creates problems that are significantly harder to fix after go-live than before. A proper data migration plan includes a source system audit, deduplication and standardization, field mapping to Salesforce objects, and post-migration validation. Minuscule's data migration services are structured around this principle.
Look for a partner with demonstrated experience in your industry, a documented implementation methodology, clear data migration and integration capabilities, and an explicit post-go-live support model. Avoid partners who are willing to skip discovery to compress timelines, or who treat go-live as the project end. References from organizations with similar complexity — particularly around ERP integrations or multi-cloud deployments - are the strongest indicator of fit.
A Salesforce implementation is only as good as the planning behind it. The technology is reliable. What varies is the rigor of discovery, the quality of data migration preparation, the depth of integration scoping, and the discipline of a partner who won't skip phases to hit a deadline.
Minuscule Technologies has delivered 75+ Salesforce implementations across manufacturing, distribution, automotive, BFSI, and other sectors. Our 160+ certified engineers have worked through every category of go-live risk — late-discovered ERP complexity, data quality surprises, under-resourced UAT, scope creep during build — and have built implementation methodologies designed to prevent them. We cover the full lifecycle, from discovery to hypercare, including SAP, PeopleSoft, and Denodo integration for organizations where the ERP is the source of truth for product and customer data.
If you are planning a Salesforce implementation and want to understand what a realistic, delay-resistant plan looks like for your organization, talk to our team.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
