ERP Implementation FAQ
ERP Implementation FAQ
Understanding ERP Systems
What is an ERP system and why does my organization need one?
An ERP (Enterprise Resource Planning) system is an integrated software platform connecting all business functions—finance, supply chain, manufacturing, HR, sales—into a single database. Instead of disconnected spreadsheets and specialized systems, ERP provides unified visibility, automated workflows, and real-time reporting. Organizations need ERP to eliminate manual data entry, improve decision-making speed, reduce errors, achieve regulatory compliance, and scale operations efficiently.
How is ERP different from our current systems?
Most organizations use point solutions: accounting software, inventory management, CRM, HR systems—all separate with manual data transfers between them. This creates silos, inefficiency, and errors. ERP unifies everything. Finance sees real-time inventory; supply chain knows customer demand automatically; HR sees payroll requirements. Data flows once, in real-time, reducing errors and providing visibility no spreadsheet ever could.
How long does an ERP implementation typically take?
Timeline depends dramatically on scope. A small business implementing basic ERP: 6-9 months. Mid-market: 12-18 months. Enterprise-scale: 24-36 months. Critical factors: data complexity, integrations required, organizational change readiness, and team involvement. Phased approaches (implementing finance first, then supply chain, then HR) extend timeline but reduce risk and allow early benefits realization.
Selection & Planning
How do I choose the right ERP system?
Selection requires disciplined evaluation: document requirements, evaluate vendors against those requirements, assess total cost of ownership (not just license cost), evaluate vendor stability and roadmap, test the software, and get references from similar organizations. Common platforms: SAP, Oracle, Microsoft Dynamics, NetSuite, Infor. No "best" system exists—the right system matches your industry, size, and specific needs. We guide this process, helping you avoid expensive mistakes.
Should we choose cloud or on-premise ERP?
Cloud ERP (SaaS): lower upfront costs, automatic updates, reduced IT overhead, accessible anywhere. On-premise: full control, customization flexibility, potentially lower ongoing costs if you have IT expertise, security comfort for regulated industries. Most organizations now choose cloud due to lower total cost of ownership and reduced IT burden. Hybrid approaches exist where some modules are cloud and others on-premise.
What does "total cost of ownership" really include?
More than license costs. TCO includes: software licensing, implementation services (biggest cost for most projects), customization and configuration, data migration, training, ongoing support and maintenance, hardware (if on-premise), and indirect costs (staff time, disruption). Honest vendors separate these clearly. Budget planning must address all components. Over 5 years, implementation services often exceed license costs for large systems.
How much customization is realistic?
Minimize customization—it's expensive and creates ongoing maintenance burden. A well-chosen ERP matches 70-80% of your needs out-of-the-box. The remaining 20-30% is typically addressed through configuration (adjusting the system to your business) rather than customization (coding changes). Excessive customization creates vendor lock-in and makes future upgrades difficult. Best practice: change your processes to fit the system where possible, customize only when absolutely necessary.
Budget & Investment
What's a realistic budget for ERP implementation?
Budget varies enormously. Small business: $500K-2M total cost over 12-18 months. Mid-market: $2-10M over 18-24 months. Enterprise: $10-100M+ over 24-36+ months. These costs include software, services (biggest component), training, and indirect costs. A useful rule: services costs often 2-3x software costs. During planning, build in 15-20% contingency for unknowns. Projects that appear low-budget often have painful surprises.
Should we expect cost overruns?
Yes, realistically. Most ERP projects experience 10-20% budget overruns due to scope creep, complexity discovered during implementation, or organizational changes. The best protection: detailed planning upfront, clear scope definition, disciplined change management, and experienced implementation partners. Budget contingency expectations accordingly. Vendors and integrators who promise "no overruns" are unrealistic.
What ROI should we expect?
Strong projects achieve: 20-30% reduction in operational costs through automation and elimination of redundant systems, 15-25% improvement in financial closing speed, 10-20% supply chain efficiency gains, improved customer service through better data visibility, and significantly improved decision-making speed. ROI realization timeline: years 1-2 break-even to modest positive, years 3-5 significant returns as you optimize processes and eliminate legacy systems.
Can we implement in phases to spread costs?
Yes—phased implementation is common and often advisable. Phase 1 (Finance & Planning): critical foundation, 6-9 months. Phase 2 (Supply Chain & Manufacturing): 6-9 months later. Phase 3 (Sales & Distribution): 6-9 months later. This spreads costs, allows early benefit realization, reduces organizational disruption, and lets you optimize each area before adding complexity. Total timeline extends, but risk and disruption reduce substantially.
Implementation Approach
What's the difference between "big bang" and phased implementation?
Big bang: implement everything simultaneously across the organization. Pros: faster overall timeline, no legacy system maintenance. Cons: extremely risky, massive organizational disruption, high failure rate. Phased: implement module by module over 18-36 months, maintaining legacy systems for non-implemented areas until they transition. Pros: manageable risk, early benefits, proven success rates. Cons: longer timeline, need to manage legacy systems temporarily, requires more change management. Most successful implementations use phased approaches.
How critical is data migration?
Data migration determines success—garbage in, garbage out. Poor migration creates years of problems. Plan migration rigorously: audit source data quality, cleanse data before migration, validate migrated data thoroughly, establish clear ownership. Plan 2-3 months for migration planning and execution alone. Budget 10-15% of project timeline just for data migration. This is not a task to rush.
What role does change management play?
Critical. ERP implementations fail most often not due to technical problems but because people struggle with change. Plan comprehensive change management: executive sponsorship, clear communication about why (not just what) is changing, training covering not just system buttons but new workflows and thinking, involve end-users early in design decisions, celebrate early wins. Organizations that invest heavily in change management have 70%+ success rates; those that minimize it have 30-40%.
How important is executive sponsorship?
Paramount. Executive sponsors champion the initiative, allocate resources, drive cultural change, and hold teams accountable. Without visible leadership support, implementation struggles with priority conflicts and resource constraints. The sponsor should be your COO or CFO—someone with authority to reallocate resources across functions. Weak sponsorship is a leading cause of project failure.
Team & Skills
Do we need an internal project management team?
Yes, absolutely. Your business owns the implementation—we provide expertise and execution, but your team drives vision and decisions. Plan dedicated resources: PMO leadership, business process owners for each module, IT resources for infrastructure and integration, change management lead. Some organizations dedicate 5-10% of payroll to implementation—that's realistic for proper execution. Part-time involvement typically leads to failure.
What skills does our IT team need?
Your IT team needs: system administration (user management, security), database administration (backups, performance tuning), system integration (connecting ERP to other systems), and ongoing support capability. If you lack these internally, budget for augmented IT staff or long-term support contracts. Most organizations maintain some internal capability but rely on vendor support and consultants for specialized expertise.
Should our team learn to maintain the system long-term?
Strongly recommended. Post-implementation, most organizations reduce external support and maintain the system internally with vendor support for complex issues. This requires training your IT team during implementation and allocating 10-15% of ongoing IT resources to ERP maintenance and optimization. Organizations that build internal capability realize better ROI; those dependent on external vendors face ongoing high costs.
Risks & Challenges
What are the biggest risks in ERP implementation?
Top risks: inadequate planning (starting without clear requirements), poor change management (inadequate training and resistance), scope creep (adding features beyond original plan), inadequate testing (bugs discovered in production), poor data quality (garbage data migrated), unrealistic timelines (compressed schedules), and weak executive sponsorship. Successful projects address these systematically.
What happens if implementation runs into serious problems?
Delays and cost overruns are common. Early warning signs: missed milestones, testing delays revealing more defects than expected, staff turnover on the project, inadequate training leading to poor adoption. Address issues immediately: conduct root cause analysis, adjust timelines and budgets accordingly, intensify change management, escalate to executive sponsors. Don't hope problems resolve themselves—they accelerate.
How do we prevent vendor lock-in?
Evaluate vendor roadmap and technology direction. Avoid excessive customization that only the vendor can modify. Ensure data can be exported (most modern ERP allows this). Maintain core IT expertise internally so you're not dependent on any single consultant. Use standard integrations where possible rather than proprietary connectors. These practices protect you long-term.
Post-Implementation
What happens after we go live?
Go-live is beginning, not end. The first 30-90 days are critical: production issues emerge, users struggle with workflows, data quality issues surface. Plan robust support, quick issue resolution, and continuous optimization. Many projects schedule intensive support for 90 days post-launch, then transition to reduced support. Expect some inefficiency initially; workflow optimization happens over months.
How do we measure success after implementation?
Establish metrics before implementation: cost reduction targets, speed improvements (order-to-cash, procure-to-pay), quality metrics, user adoption rates, system availability/performance. Measure at 90 days, 6 months, 1 year, and 3 years. Be patient—benefits fully realize over 12-24 months as teams adapt and optimize. Track not just quantitative metrics but qualitative improvements: decision-making speed, visibility, employee satisfaction.
Ready to Explore ERP Implementation?
Schedule a consultation to assess whether ERP makes sense for your organization and what implementation might look like.