A failed Salesforce implementation costs more than the licence fees. It costs months of lost productivity, frustrated users who revert to spreadsheets, and a C-suite that never trusts CRM again.
We have seen every one of these mistakes. Some we caught early. Some we inherited from other partners and had to untangle. After more than a decade of Salesforce delivery across the Philippines and Australia, these are the ten that keep showing up.
If you are planning a Salesforce implementation in the Philippines, treat this list as your pre-flight checklist.
Key Takeaways
- Discovery is not optional — skipping it is the single most expensive shortcut in any Salesforce implementation
- Adoption is a people problem, not a technical one, and it must start before go-live
- Data migration without cleansing creates a CRM nobody trusts
- The right partner has delivery experience, not just certifications on paper
1. Skipping Discovery and Jumping Straight to Configuration
This is the most expensive shortcut in Salesforce implementation. Companies want to see screens, so the partner starts building before anyone agrees on what “done” looks like.
The result? Rework. An airline client came to us after their previous partner built out a Service Cloud org based on assumptions from a single kickoff meeting. Three months and six figures later, it did not match how their ground crew actually worked.
What to watch for: If your partner starts configuring in Week 1 without a signed-off process map, that is a red flag.
2. Treating Salesforce Implementation Like an IT Project
Salesforce is a business transformation, not a software install. When IT owns the project in isolation, the org gets built around technical requirements rather than how sales reps, service agents, or marketers actually do their jobs.
The most successful implementations we have delivered in the Philippines had a business sponsor — a VP of Sales or Head of Operations — driving requirements alongside IT. The technology team handles architecture. The business team defines what success looks like.
Bottom line: If your project steering committee has no one from the business side, you are building the wrong thing.
3. Migrating Dirty Data Without a Cleansing Strategy
Bad data in means bad data out — except now it is in a system everyone can see. Companies rush to migrate millions of records from legacy CRMs or Excel files without deduplication, validation, or field mapping.
A pharmaceutical company we worked with had 40,000 physician records across three spreadsheets. Over 12,000 were duplicates. Another 8,000 had incomplete addresses. Migrating all of that into Salesforce would have destroyed user trust on day one.
| Data Issue | Impact on Salesforce |
|---|---|
| Duplicate records | Reps waste time, reporting is inflated |
| Missing fields | Automation and workflows break silently |
| Inconsistent formats | Filters and reports return wrong results |
What to watch for: Your partner should present a data audit and cleansing plan before any migration begins.
4. Building Custom Apex When Declarative Tools Would Suffice
Over-engineering is a quiet budget killer. Salesforce Flows, validation rules, and formula fields handle the majority of business logic without a single line of code. But some partners default to custom Apex because it is what their developers know.
The problem surfaces later. Custom code requires developer resources to maintain. Flows can be modified by trained admins. When a financial services client needed a simple approval routing change, their previous partner quoted two weeks of Apex development. We rebuilt it as a Flow in a day.
Bottom line: Ask your partner to justify every piece of custom code. If a declarative tool can do it, it should.
5. Ignoring User Adoption Until After Go-Live
You can build a technically perfect org that nobody uses. Adoption is not a training session in the last week before launch. It is change management that starts during discovery and continues for months after go-live.
We have seen this pattern repeatedly in Philippine enterprises: leadership buys Salesforce, IT implements it, and on launch day the sales team opens it for the first time. Confusion turns to resentment. Within weeks, reps are back in Excel.
Adoption essentials:
- Champions identified per department during discovery
- Users involved in UAT — not just testers, actual daily users
- Post-go-live office hours for the first 60 days
- Quick wins delivered early so users see value immediately
6. Not Planning for Integrations Early Enough
Salesforce rarely lives alone. It connects to ERP systems, payment gateways, marketing platforms, and custom databases. When integration planning starts after the core build, timelines blow out.
A healthcare client needed their Salesforce org to sync with an existing patient management system. That requirement surfaced in Week 8 of a 12-week project. The integration alone needed six weeks. Do the maths.
What to watch for: Your implementation partner should map every integration point during discovery — not as a Phase 2 afterthought.
7. Choosing a Partner Based on Certifications Alone
Certifications prove someone passed an exam. They do not prove someone can deliver. The Philippine market has no shortage of certified Salesforce professionals. What is rarer is a partner with a track record of completed implementations in your industry.
| What to Evaluate | Why It Matters |
|---|---|
| Years of delivery experience | Proves they have survived real projects |
| Industry-specific implementations | They understand your workflows, not just the platform |
| Team stability | High turnover means your project gets handed off mid-stream |
| Post-go-live support model | Implementation is only the beginning |
For a deeper dive on this, read our guide on 5 questions to ask before hiring a Salesforce consultant in the Philippines.
8. Underestimating Marketing Cloud Complexity
Marketing Cloud is not Sales Cloud with emails. It is an entirely different platform with its own data model, its own scripting language (AMPscript), and its own learning curve. Companies that bundle it into a Sales Cloud implementation timeline are consistently surprised.
We have seen Philippine companies purchase Marketing Cloud licences, attempt a self-implementation, and abandon it within three months. The platform is powerful — but it demands dedicated expertise and a separate implementation timeline.
Bottom line: If Marketing Cloud is in scope, budget for it as a standalone workstream with its own discovery and go-live date.
9. No Post-Go-Live Support Plan
Go-live is not the finish line. The first 90 days after launch are when real usage patterns emerge, edge cases surface, and users need the most support.
Companies that cut ties with their implementation partner at go-live end up with an org that slowly degrades. Fields get misused. Workarounds become habits. Reports stop being trusted.
A proper support plan includes:
- Dedicated admin resource (internal or outsourced)
- Monthly health checks for the first quarter
- A backlog process for enhancement requests
- Defined escalation path for platform issues
10. Trying to Replicate the Old System Instead of Rethinking Processes
“Make it work exactly like our old CRM” is the most dangerous requirement. If the old system worked perfectly, you would not be replacing it. Salesforce implementation is an opportunity to fix broken processes — not to pave the cow path with more expensive technology.
An airline client initially wanted every field from their legacy system recreated in Salesforce. That was over 200 fields per record, most of which nobody used. We ran a field utilisation audit and found that only 35% of those fields had been updated in the past year.
What to watch for: If your requirements document is a screenshot of your old system, pause and ask which processes actually need to carry forward.
How to Avoid These Mistakes
Most of these come down to two things: choosing the right partner and investing in discovery.
A strong Salesforce implementation partner will push back when you try to skip steps. They will insist on data cleansing before migration, flag integration risks early, and build adoption into the project plan from day one.
We are building our complete guide to Salesforce implementation in the Philippines — a step-by-step walkthrough of timeline, cost, and what actually happens from kickoff to go-live.
In the meantime, if you are evaluating partners, our consultant hiring guide and Salesforce consulting overview are good starting points.
Why Aether Global Technology Inc.
Aether Global Technology Inc. was founded in 2023 with roots dating back to 2011 — over a decade of Salesforce delivery across the Philippines and Australia.
We work across Sales Cloud, Service Cloud, Marketing Cloud, and MuleSoft. Our verticals include aviation, healthcare, pharmaceutical, financial services, and legal. Our team’s average tenure exceeds three years, which means the people who start your project are the people who finish it.
Frequently Asked Questions
What is the most common Salesforce implementation mistake in the Philippines?
Skipping or rushing the discovery phase. Philippine companies often want to see results quickly, which leads to configuration starting before business processes are properly mapped. This almost always results in costly rework and extended timelines. A proper discovery takes two to four weeks and saves months downstream.
How long does a typical Salesforce implementation take?
Three to six months for a standard Sales Cloud or Service Cloud deployment. Complexity increases with integrations, data migration volume, and multi-cloud scope. Marketing Cloud adds its own timeline. The biggest schedule risk is not technical — it is unclear requirements and delayed stakeholder feedback.
Should we hire an in-house Salesforce team or use an implementation partner?
Use a partner for implementation, then evaluate your ongoing needs. Building an in-house team before you have a live org means paying salaries during a phase where specialised implementation experience matters most. Post-go-live, a managed services arrangement lets you scale your internal team gradually.
—
Ready to discuss your Salesforce implementation? Talk to our team — no pressure, just a conversation about what you are trying to achieve.
