News

Software Implementation: Steps and Mistakes

· DigifyNow

Auf Deutsch lesen

A software implementation works when three things are settled before go-live: the new process for each role, written acceptance criteria, and a data migration that has been test-run at least once. Key users then train colleagues on real cases. You switch over on a cutover date or through a pilot group, and the old system stays read-only. Most failures come from leaving the old way open in parallel and having no one own the new software.

A software implementation covers everything from the decision to adopt a program up to the day the process runs only in that program and the old way is shut down. It happens in eight steps: define the goal and who owns it, map the current process, write acceptance criteria, choose a solution, prepare the data with a trial migration, set up permissions and integrations, run a pilot with key users, then cut over and provide follow-up support. Two things make the difference: a trial migration before the cutover date, and one person who stays responsible for the software after launch.

What does a software implementation include?

Installing software often takes no more than an afternoon. But software is only implemented once the process it is supposed to support actually runs in it and the old way of doing that work is closed. That is why a software implementation includes five work packages: planning and selection, customization and integrations, data migration, training, and support once the system is live. If you only buy the tool, you end up with two systems instead of one. People keep maintaining customer data in the Excel sheet and at some point start entering it into the new program as well.

An example: a trades business rolls out a job management system. Technically, everything is done once the software is running. It is only implemented when the office creates jobs exclusively there, the field technicians update the status from their phones, and the invoice is generated from the job instead of from a Word template. Each of these points is a decision that has to be made before launch: Who creates jobs? Which fields are mandatory? What happens to the open jobs in the old system?

Illustration for the question "What does a software implementation include?"
AI-generated image

How to implement software: the steps at a glance

  1. Define the goal and ownership: Which process should change, how will you notice (for example, how long a job takes from start to finish, or how many follow-up questions land in the office), and who makes the call when people disagree? Without a named owner, open issues just sit there.
  2. Map the current process: step by step, with roles, documents and every point where information gets copied from one medium to another. That includes the special cases only one person knows about.
  3. Write down requirements and acceptance criteria: Separate must-haves from nice-to-haves and turn real transactions into test cases that the system will later be signed off against.
  4. Choose a solution: off-the-shelf software, a SaaS subscription or custom development, each measured against the must-have criteria and the integrations you need.
  5. Prepare the data: Clean up duplicates, map fields from the old system to the new one, run a trial migration and reconcile record counts and totals against the old system.
  6. Set up permissions, integrations and a test environment: roles and access rights for each user group, connections to accounting, your online store or email, and tests with copies of real data.
  7. Train key users and run a pilot: A small group works with the software first, reports bugs and then trains their colleagues.
  8. Cut over and support: Set a cutover date, switch the old system to read-only and provide a fixed point of contact for questions during the first few weeks.

For step two, a structured process analysis with a template helps. For step four, it is worth asking whether custom software or SaaS is the better fit in your specific case. Most people underestimate step five. What a trial run and reconciliation look like is covered in our article on data migration with a checklist.

An example for step three: instead of "able to create quotes," the acceptance criterion reads "A quote with three line items, a discount and a different delivery address can be created, sent as a PDF and converted into an order without re-entering anything." On sign-off day, a sentence like that is either checked off or it isn't. A separate article shows what this looks like in a CRM implementation with pipeline stages and mandatory fields.

How does change management work in a software rollout?

In a software rollout, change management does not mean keeping everyone in a good mood. It means telling each role in advance what will change in their workday. Accounting wants to know whether receipts will reach them differently. The sales reps in the field want to know whether they will still be typing up reports in the evening. If nobody answers, people fill the gap with assumptions, and that is where the resistance comes from that later gets labeled an adoption problem.

  • Name key users early: one person per department who has a say in the requirements, tests during the pilot and then becomes the first point of contact for colleagues. They need time for this that is genuinely freed up from their day-to-day work.
  • Train on real cases: Training with sample data doesn't stick. People should take one of their own jobs or customers all the way through the new system from start to finish.
  • Close the old way: As long as the Excel sheet can still be edited, it will keep being used. From the cutover date on, the old system should be read-only.
  • Set up a channel for issues: one place where problems are collected and prioritized, instead of every question being shouted across the room to management.

What doesn't work: a rollout that management announces and then doesn't use itself. If approvals keep going through email instead of the system, employees take that as a signal that the old way still works too.

Illustration for the question "How does change management work in a software rollout?"
AI-generated image

Cutover date, pilot or parallel run: how do you switch over?

How you switch over determines both the risk and the effort. The four common approaches can be measured against the same questions.

Cutover approaches in a software implementation, as of October 2026
Cutover approachHow it worksFits whenWhere it gets stuck
Cutover date (big bang)Everyone switches on the same day, and the old system becomes read-only at the same timefew users, one clearly defined process, trial migration ran cleanlyOne error hits everyone at once. Without a rollback plan tested in advance, operations come to a halt.
Pilot groupOne department or location goes first, the others followseveral teams with a similar processBetween the pilot and everyone else, data lives in two systems. Handoffs have to be clearly defined.
Phased by functionFirst contacts, for example, then quotes, then invoiceslarge software with separate modulesInterfaces between old and new are needed for the transition period, and they take effort.
Parallel runOld and new run side by side for a while and results are comparedbilling or payroll, where discrepancies have to show up immediatelyDouble data entry weighs on the team. Without a fixed end date, the parallel run becomes permanent.

For small businesses with a single process, a cutover date is often the most honest approach, provided the trial migration ran completely and there is a written plan for what happens if something doesn't work on day one.

An example of a pilot group: a business with an office and a field team first moves only the office to the new job management system. For two or three weeks, the technicians still phone in their status and the office enters it. Only once job creation, status updates and invoicing run reliably in the office does the field team get the mobile view. That way you can tell whether an error lies in the process or in how the app is used out in the field.

Why do software implementations fail?

  • Requirements only after purchase: The software is chosen based on the demo and the price, and the special cases only surface once it's live. Then it gets customized after the fact, or people work around it.
  • No acceptance criteria: Without written test cases, nobody has defined when something is finished. The discussion about it never ends.
  • Data migration as the last step: Wrong character encodings, duplicate customers or missing mandatory fields only show up on the cutover date if there was no trial run.
  • Integrations underestimated: The software can export, but accounting imports a different format. In the end, someone retypes everything by hand.
  • No one responsible after launch: Updates, new users, permissions and bug reports need an owner. Without one, the system gradually turns into a mess.
  • Too much at once: If you switch five processes at the same time, you can hardly track down the cause of an error.

Some implementations aren't worth doing at all. If a process is rarely used and isn't connected to other systems, a clean spreadsheet with clear rules is often a better solution than a new program that has to be maintained. If someone clicks through an old interface with no API every day, a software robot can be a stopgap. A separate article covers where RPA works for small businesses and where it breaks down when the interface gets updated.

Illustration for the question "Why do software implementations fail?"
AI-generated image

Software project vs. software implementation: what's the difference?

A software project builds or changes software: requirements, development, testing, sign-off. A software implementation puts finished or newly built software into operation: data, permissions, training, cutover, follow-up support. With off-the-shelf software, there is often only the implementation. With custom software, the two are linked, and the implementation should already be part of the project plan. Otherwise the software gets signed off, but nobody has planned the migration and the training. How a development project runs in phases through to sign-off is described in our article on the process when you hire a team for custom software development. Whether a solution of your own is worth it in the first place is covered in our article on custom software for small and mid-sized businesses.

Does software need to be available 24/7 after implementation?

Whether software has to run 24 hours a day depends on the process, not the software. A customer portal, an online store or an app for technicians working in shifts needs around-the-clock operation. That means monitoring that alerts you when something goes down, backups with tested restores, and someone who can respond outside office hours. For an internal job management system that is only used on weekdays, an evening maintenance window for updates is usually enough. Settle this before you choose a solution. With SaaS, availability and maintenance windows are spelled out in the vendor's contract; with self-hosted software, you or your service provider are responsible for operations. A statement like "it runs in the cloud" doesn't tell you anything about this yet.

Illustration for the question "Does software need to be available 24/7 after implementation?"
AI-generated image

What else applies if the new software uses AI?

If you introduce an AI assistant or another AI system, the European AI Act, in its most recently amended version, comes into play. It requires providers and deployers to take measures to support the development of AI literacy among their staff and other persons who deal with the operation and use of the system on their behalf. They do not have to guarantee a particular level of literacy for any individual. In practice, this means training on the system's limits and typical failure patterns belongs in the implementation plan, for example the fact that a language model can state false information convincingly and that results have to be checked.

In addition, transparency obligations already apply to systems that generate text, images, audio or video. For systems that were placed on the market before that, providers have a transition period. The stricter rules for high-risk systems only take effect later, in stages. Which obligations and deadlines apply to your case is a legal question and belongs with someone who gives you legal advice; the binding source is the text of the regulation, which you can find on EUR-Lex. How an implementation works specifically for AI assistants is described in our article on how to implement an AI assistant in your company.

How DigifyNow supports an implementation

DigifyNow develops custom apps, web apps and software for small and mid-sized businesses and introduces AI into companies. For us, the implementation is part of the job: a first MVP with the core function typically takes four to eight weeks and is tested with a pilot group on real cases before more features are added. With AI systems, we train and support the employees who work with them. The duration and scope of a specific project depend on integrations, the state of the data and operations, and can only be stated after an assessment. You'll find an overview of App, software and AI services from DigifyNow on our services page.

From our project work: for Mundo Marketing, we developed a custom back office with a CRM. With systems like this, we move the implementation questions up front. Who gets which role, which legacy data is carried over and who the internal contact person is — we settle that before development, not after sign-off. We involve the key user early so they test processes on an early build and not only on the finished system. You can read more in our case study on the back office for Mundo Marketing.

Illustration for the section "How DigifyNow supports an implementation"
AI-generated image

When outside help is worth it

Outside help is worth it when the new software has to be connected to existing systems such as accounting, an online store or a CRM, when legacy data comes from several sources, or when no suitable off-the-shelf software exists. For a single SaaS tool without integrations, many businesses manage the implementation on their own using the steps above. For a conversation, have a short description of the process ready, along with the roles involved, the systems you already use and a sample of real data. In a free, no-obligation assessment of your project, we look at it together and also tell you if a solution of your own isn't worth it.

Frequently asked questions

What is a software implementation?

A software implementation brings a program into everyday work: planning and selection, customization and integrations, data migration, training and support during operation. Unlike installation, it is only complete when the process runs exclusively in the new software and the old system is read-only. A software project builds the software; the implementation puts it into operation.

What are the phases of a software implementation?

Typically there are eight steps in four phases. Preparation: goal, ownership, current process and acceptance criteria. Selection: off-the-shelf software, SaaS or custom development, measured against the must-have criteria. Execution: clean up the data and run a trial migration, set up permissions and integrations. Operation: pilot with key users, cutover by date or pilot group, and follow-up support with a fixed point of contact.

How long does a software implementation take?

It depends on three factors: the number of processes being switched over, the state of the legacy data and the number of integrations. A single SaaS tool for one team is implemented faster than a system that brings together quotes, orders and invoices. The longest phase is rarely the technology; it is usually the data cleanup and the time until everyone works in the new process.

What is a key user?

A key user is an employee from the business department, not an IT specialist. They contribute their department's requirements, test during the pilot, then train their colleagues and remain the first point of contact for questions. Unlike external training, they know the special cases of their own process. For this, they need time that is genuinely freed up from day-to-day work.

Should you delete the old system after implementation?

No, not right away. After the cutover date, the old system is set to read-only so nobody keeps working in it, but old records can still be looked up. It is only shut down once the migration has been reconciled and it is clear how long the data must be retained. You should check that with your tax advisor.

How much does a software implementation cost?

There is no flat figure. Costs are made up of licenses or development, customization, integrations, data migration, employees' training time and ongoing operation. The internal time for key users and testing is often forgotten, even though it belongs in the plan. A reliable number only emerges once the processes, data volume and integrations are known.

Request a free assessment of your project