ERP Implementation: What to Expect and Who You'll Be Working With

Your legacy system is a museum exhibit. You know it. Your auditors know it. And your staff definitely knows it. (Especially during month-end close when the system crashes for the third time in a week.)

That's why you've decided to modernize. Congratulations!

But now comes the process of implementing...

Let's talk about what actually happens between signing the contract and going live with your new ERP system.

How Long Does an ERP Implementation Take?

Some vendors promise you'll be up and running in 90 days. Others might not commit to a timeline at all. But honestly, it depends. We know you hate that answer, but it's the honest truth.

Here's the reality based on industry data:

Full enterprise ERP implementations can take 6 to 18 months. This includes core financials, purchasing, budgeting, payroll, HR, and utility billing working together as a unified system.

But that's just the baseline. Your actual timeline depends on three critical factors that can extend implementation by 30% or more beyond initial estimates.

1. Module count is the first variable.

   Each additional department you bring onto the new system adds around 3 to 6 months to your project. Starting with just core financials, you might go live in 6 to 9 months. Adding payroll and HR? Tack on another 3 to 6 months. A city implementing core financial modules sees faster rollouts than one attempting a full enterprise suite with community development, permitting, and inspections all at once.

2. Data migration depth is critical.

   Reconciling 2+ years of legacy data is the primary cause of implementation delays.  You're converting decades of property tax records, payroll history, and utility consumption data into a modern relational database. Every accounts payable invoice. Every check payment. Every utility billing transaction. All of it has to reconcile perfectly.

   If your legacy data lives in a standard system with clean exports, you're in good shape. Converting from one recognized platform to another is predictable. But if your data is scattered across Excel spreadsheets, paper records, or a highly customized system... Add additional time just for data cleaning before implementation can even begin.

3. Organizational readiness.

   Challenges with project governance, internal leadership alignment, and the scale of the change itself create more timeline overruns than true technical failures. You're asking finance staff to learn new workflows while still closing the books each month. You're asking Payroll to adopt new processes without missing a single paycheck.

   The most successful implementations treat this transition as a period of business process re-engineering—not just another software installation.

Every successful ERP implementation follows a structured path, but each organization is different with varied needs.

Skip a phase or rush through it, and you'll pay for it later with degraded data quality, poor user adoption, or extended stabilization periods. Maybe employees won't get a handle on the system as fast as you'd thought. Maybe there will be scheduling conflicts. Maybe one department will cause some pushback. You never know, but there is a best-case scenario.

We've built out a timeline (based on our implementation process) so you can get an idea of how long each phase takes, and how to be successful every step of the way.

Phase 1: Discovery and Planning (~1-2 months)

This is where we map your current reality.

We review your existing business processes. We identify your pain points. We document your workflows. And we figure out what can stay the same and what needs to change.

This phase might take longer than you think it should. But spending more time on preparation helps you avoid mid-project failures.

Industry trends show organizations are dedicating more resources to front-end planning specifically because it prevents expensive problems later.

You'll work with a project manager to establish realistic milestones. You'll identify your power users in each department. And you'll create a communication plan for keeping all involved parties informed throughout the project.

The discovery phase also includes a technical assessment: evaluating the quality of your legacy data.

If we find problems here (duplicate vendor records, unreconciled balances, inactive accounts that were never archived, etc.), we address them now before they become migration nightmares.

Phase 2: Configuration (~1 month)

Now we build your initial system configuration. Our initial configuration takes about 1 month (we can't speak for other vendors).

We set up your chart of accounts. We configure your approval workflows. We customize forms, reports, and dashboards. We establish user roles and permissions. And we align the software to your specific operational needs.

As you know, government accounting has unique requirements: fund accounting, GASB compliance, GAAP standards, and audit trails. All of that is taken into account.

We continue to tweak the configuration throughout Phase 4 (the internship) as you test and train. (Don't worry, we'll get to this.)

As your team works in the system during testing and training, you'll discover adjustments that need to be made. We refine workflows, modify reports, and adjust settings based on real-world use.

You're also not locked into decisions made during month one. The system evolves as your understanding of it deepens.

Process re-engineering also happens during this phase.

Maybe your current accounts payable process involves seven approval steps and takes 45 days. The new system can reduce that to three steps and 10 days. (But only if you're willing to change your internal procedures.)

That requires buy-in from department heads, city managers, and sometimes even your city council.

Phase 3: Data Migration (Up to 6 months)

This is the phase that makes or breaks an implementation.

Data migration is consistently cited as the single most common cause for ERP implementation delays.

For new conversions, we have recently seen data migration take up to 6 months. We don't hand you a template and say "good luck reformatting your data." We extract it from your legacy system. We map it to the new database structure. We convert it. And we validate every single balance.

Here's what gets migrated:

• General ledger detail and balances

• Accounts payable invoices and payment history

• Accounts receivable transactions

• Budget data from previous fiscal years

• Payroll history and employee records

• Utility billing consumption and payment history

• Property tax records

• Check history and bank reconciliations

The complexity depends entirely on your source data quality. Converting from a standard platform is straightforward. Converting from a custom or heavily modified system requires significantly more work.

While the conversion team is busy at work creating the sandbox, we are preparing you for your internship by practicing in a fake environment.

You're not sitting idle waiting for data migration to complete. You're learning the system, building muscle memory, and getting comfortable with new workflows using practice data.

And by the time your real data is converted and loaded into the sandbox, your team is already trained and ready to validate it.

Phase 4: Internship (~20 weeks / 5 months)

We call this phase "the internship" because it's where your team becomes proficient through hands-on practice.

A standard internship is 20 weeks (roughly 5 months). This isn't passive classroom training, either. We both test and train during this phase by completing parallels.

What are parallels, you may ask? Well, they're real-world scenarios where your team processes actual transactions in the new system while simultaneously processing them in your legacy system.

We typically spend 1-2 hours per week with you to research and practice in the new system. Outside of meetings with us, you can expect to spend an additional 1-2 hours doing exercises with your team. Altogether, you can expect to spend 2-4 hours a week getting adjusted to your new system.

And as long as you and your team are progressing and we’re able to keep configuration and training on track, we’re open to creating a schedule that works best for you.

You compare results. You identify discrepancies. You learn by doing.

And during the internship, if applicable, you and your team will:

• Process payroll runs in both systems and compare outputs

• Generate utility bills in parallel and validate amounts

• Complete month-end close procedures simultaneously

• Run financial reports side-by-side to verify accuracy

• Test budget amendments, journal entries, and reconciliations

This approach serves two critical purposes:

1. First, it validates that the system is configured correctly. If parallel processing reveals discrepancies, we identify whether it's a configuration issue, a data problem, or a workflow difference. We make adjustments and continue testing until the results match perfectly.

2. Second, it builds confidence. Your staff isn't just learning how to click buttons. They're proving to themselves that the new system produces accurate results. By the time you go live, they've already processed real transactions successfully. The fear of the unknown is gone.

Your staff gets access to the sandbox environment with their actual converted data.

They can practice transactions, run reports, and experiment without risk of breaking anything. But unlike traditional training environments with fake data, they're working with their real chart of accounts, their actual vendors, and their genuine utility customers.

We'll identify power users in each department and give them advanced training. They become internal experts who can help their colleagues and troubleshoot routine issues. By the end of the 20-week internship, these power users are fully proficient and ready to support the broader team.

Other vendors might compress training into a few weeks. We give you months of hands-on practice because we know that's what it takes to truly master a new system while maintaining your daily operations.

Phase 5: Go-Live and Stabilization (~1-3 months)

The system is live. Your real work begins now.

The technical go-live of an ERP system is only one milestone. Ultimate success depends on staff adoption and maintaining high data quality as users adjust to new workflows.

Projects that fail to account for this human-centric phase often see data quality degradation.

Users might struggle to adapt while maintaining their regular responsibilities. Small mistakes compound. And suddenly, your clean data migration is corrupted by incorrect journal entries and unreconciled balances.

So we stay engaged. We troubleshoot. We retrain where needed. And we don't consider the implementation complete until your team is operating confidently and your data integrity is solid.

Then, when fully confident, you are turned over to Customer Support for all your future questions and needs.

Who You'll Be Working With

• Your Project Manager

  This person coordinates everything. They set timelines, track milestones, manage dependencies, and keep everyone aligned. You'll communicate with your project manager weekly—sometimes daily—during critical phases. They're your main point of contact for questions, concerns, and status updates.
  A good project manager protects you from uncontrolled project expansion. They push back when timelines become unrealistic. And they escalate issues before they become crises.

• Implementation Consultants

  These are the people who configure your system and lead your training sessions.  They understand government accounting inside and out (at least, they do at SSI). They've seen how hundreds of municipalities handle fund accounting, GASB reporting, and audit compliance. And they bring that experience to your implementation.
  Implementation consultants work closely with your department heads during the configuration phase. They facilitate those intensive workshops. They translate your business requirements into system specifications. And they recommend best practices based on what works for similar organizations.

• Data Migration Specialist

  These technical experts handle the complex work of converting your historical records. They write the extraction scripts. They build the mapping tables. And they validate that every balance reconciles between your old system and your new one.
  Data migration specialists understand database structures, data normalization, and referential integrity. They identify problems in your source data that could cause migration failures. And they clean up those problems before conversion runs.

• Your Internal Team

  Your vendor provides expertise. But your internal team drives the project. You need a project champion who has executive authority to make decisions and remove obstacles. You need power users from each department who will become system experts and help train their colleagues. And you need executive sponsorship from your city manager or county administrator who can communicate the importance of this project and allocate necessary resources. Implementation work can't happen in spare moments between regular duties. Your team needs protected hours to review configurations, attend training, and test the system.

How to Speed Up Success (Without Rushing)

You can't force a faster timeline. But you can eliminate delays. Here's how:

Clean Your Data Early

Don't wait for us to identify problems in your legacy data. Start cleaning now.

Identify duplicate vendor records and merge them. Reconcile old balances that don't match between systems. Archive inactive accounts, employees, and utility customers. Document any unusual transactions or adjustments from previous years.

The cleaner your source data, the faster the migration goes.

Assign Dedicated Records

Implementation work requires focused attention. Your team can't configure workflows, attend training sessions, and test the system in the 30 minutes between meetings.

Protect staff time for implementation activities. Adjust workloads in other areas. Bring in temporary help for routine tasks if necessary.

Organizations that treat implementation as "extra work on top of everything else" consistently miss deadlines and experience poor adoption.

Make Decisions Quickly

Every delayed decision pushes your timeline back.

When we ask "how do you want to handle requisition approvals?", respond within days, not weeks.

When we present configuration options, evaluate them promptly and choose one.

When we identify problems in your legacy data, we address them immediately.

Indecision is expensive. It idles consultants. It creates bottlenecks. And it extends your implementation by weeks or months.

Align with Your Fiscal Calendar

Most governments prefer to go live at the start of a fiscal year. This makes sense—you're not dealing with mid-year transitions or split-year reporting.

Work backward from your target go-live date. If you want to launch on July 1st, you need to start implementation planning no later than the previous summer. That gives you 12 months for a full enterprise implementation.

Trying to compress timelines to meet an arbitrary deadline is how implementations fail. Respect the calendar. Respect the process. And give yourself enough time to do it right.

Phase Your Rollout

Don't try to implement everything simultaneously.

Start with core financial modules: general ledger, accounts payable, accounts receivable, and budgeting. Get those stable and validated. Then add payroll and HR. Then add utility billing.

This staggered approach is a strategic necessity. The integrity of your financial foundation must be validated before complex employee-facing and revenue-generating modules are activated.

Phased rollouts reduce the risk of failure. They let your staff learn the system gradually. And they give you wins along the way instead of betting everything on a single big-bang launch.

What About Our Historical Data?

This question might keep you awake at night.

You need historical data for audits. You need it for trend analysis and budget forecasting. You need it for legal compliance. Losing it would be a nightmare.

So let's be specific about what gets migrated and how we protect it.

What Gets Converted

We will typically migrate 2 years of historical data. But timelines can change depending on how many years of historical data you want to migrate.  The data migration includes:

General Ledger: Every transaction, every journal entry, every fund balance from the past decade. You'll be able to run comparative financial reports, trace historical expenditures, and provide complete audit trails.

Accounts Payable: Every invoice, every payment, every vendor interaction. If an auditor asks about a payment from six years ago, you'll have the complete record.

Accounts Receivable: Every billing, every payment received, every aging balance. Historical collection patterns inform your budget projections.

Budget Data: Adopted budgets, amendments, and actuals from previous fiscal years. You need this for variance analysis and trend forecasting.

Payroll History: Employee earnings, withholdings, and employer contributions. This is critical for W-2 preparation, retirement reporting, and resolving employee inquiries.

Utility Billing: Consumption history, payment records, and customer account details. You need consumption patterns for rate studies and revenue projections.

Check History: Every check issued, every bank reconciliation, every voided transaction. You maintain complete banking records without gaps.

What If Our Legacy Data is Messy?

Then we deal with it together.

If your data is stuck in Excel spreadsheets or physical paper records, we'll add a phase for data cleaning. This could add some time to the process, but it's necessary.

If your legacy system has been heavily customized or uses non-standard data structures, we'll allocate extra time for custom extraction scripts and manual validation.

We've migrated data from ancient systems, outdated mainframes, and custom databases built by consultants who retired 15 years ago. It's not always pretty. But it's almost always doable.

The key is honesty. If you know your data has problems, let us know upfront. We'd much rather plan for complexity than discover it mid-project.

The Reality of Change Management

Technical implementation is only half the battle. The other half is getting your team to actually use the new system.

Change is hard. Your team has muscle memory built on years of using the old system. They know exactly which buttons to click, which reports to run, and which workarounds to use when something breaks.

A new system disrupts all of that. Even if the new system is objectively better, it feels harder at first because of the learning curve.

• Some staff worry about job security. "If the new system automates my work, will I still be needed?"

• Some resent the time investment. "I'm too busy to learn a new system right now."

• And some just don't see the point. "The old system worked fine for 20 years. Why change?"

So how do I build buy-in across my team? 

Start communicating early. Before you even sign the contract, explain to staff why you're modernizing. Talk about the problems with the legacy system: crashes, slow performance, security vulnerabilities, inability to produce modern reports, etc.

Involve staff in the process. Include department representatives in configuration workshops. Let them test the system and provide feedback. When people feel heard, they're more likely to support the change.

Celebrate quick wins. When the new system does something better than the old one (faster month-end close, easier budget amendments, automated utility billing), highlight it. Show your team that this change benefits them directly.

Provide adequate training time. Don't expect staff to learn the new system in a single 2-hour session. Give them hands-on practice time. Let them make mistakes in the training environment. Answer their questions patiently.

Acknowledge the difficulty. Don't pretend this transition is easy. Recognize that staff are learning new skills while maintaining their regular workload. Express appreciation for their flexibility and effort.

Change management is the difference between a successful implementation and one that technically goes live but never achieves full adoption.

"When customers are resistant to change, consultants engage more deeply by completing the process alongside the customer in their legacy system and then demonstrating how the same process can be efficiently performed within VIP.

In most cases, once customers gain a comprehensive understanding of the reasoning behind VIP’s best practices and transaction workflows, they are more willing to adopt the necessary internal procedural changes. Even when initial resistance persists, customers typically become more comfortable and trusting of the system after spending time working within VIP, which leads them to align more closely with recommended best practices."

 - Danielle W., Customer Success Advocate

Questions to Ask Other Vendors

When you're evaluating ERP providers, these questions will reveal a lot about their approach:

1. What's your average implementation timeline for organizations of our size?

   • If they promise 90 days for a full ERP replacement, they're either misleading you or they don't understand your responsibilities.

2. How many hours per week will this require from our team?

   • If they say 40 hours per week, ask yourself whether that's sustainable. Your staff can't abandon their regular duties for months.

3. Who owns the data migration process?

   • If they hand you a template and expect you to reformat your own data, plan for delays and problems.

4. What training is included in the contract?

   • Make them specify: hours of training, role-based sessions, post-go-live support, training materials provided, etc.

5. What happens during the stabilization period after go-live?

   • If they don't have a clear plan, you'll struggle during those first critical weeks.

6. Can you provide references from similar organizations?

   • Talk to their existing customers. Ask about timeline accuracy, data migration quality, training adequacy, and post-go-live support.

The answers will tell you whether they respect your organization's capacity and understand the complexity of government ERP implementations.

And some vendors compete on speed. "We'll have you live in 3 months!" they promise. But unless they are for one small module, fast implementations often fail. 

• Insufficient data cleaning: If you rush the pre-implementation phase, you might migrate bad data that corrupts your new system.

• Inadequate Training: Compress the training timeline, and your staff might go live unprepared. They'll make mistakes. And get frustrated. And they'll revert to workarounds that undermine the new system.

• Poor Process Engineering: If you skip the configuration workshops, you'll get an out-of-the-box system that doesn't match how your organization actually operates.

• No stabilization period: Launch too soon, and you're on your own when problems arise.

Just remember that speed isn't necessarily the goal. A well-planned, 12-month implementation that delivers clean data, confident users, and stable operations is infinitely better than a rushed 6-month project that crashes and burns.

Quick Recap

Here's what you need to remember:

• Plan for 6 to 12 months for a full ERP implementation. Module count, data quality, and organizational readiness will determine where you fall in that range.

• Expect five distinct phases: discovery, configuration, data migration, training, and go-live. Each phase matters. Don't skip steps.

• Your implementation team will include project managers, consultants, data specialists, and technical support. But your internal team (your project champion and your power users) are just as critical.

• Data migration is the invisible timeline extender. Clean your legacy data early. And don't accept a one-shot migration approach.

• Training is ongoing, not one-time. Your staff need pre-go-live preparation, hands-on practice, support, and continued education as they grow into the system.

And remember: we don't spend 40 hours per week on implementation because that approach doesn't work. Smart implementation wins against fast implementation every time.

Good implementations are built on honest communication, careful planning, and mutual respect for the complexity of government operations.

If you're ready to start this conversation (with realistic expectations and honest timelines), let's talk. Your legacy system isn't getting any younger. Or, you could continue to have software that crashes during year-end...

I'd rather learn about your support...