How long an enova365 implementation takes: stages, timelines and what most often delays it
Implementing a single enova365 module in a small business usually takes 3 to 6 weeks, and a multi-module environment up to 6 months. We describe the stages of the schedule, how long each one takes, and which decisions on the company's side affect the deadline more than the configuration itself.
An ERP deadline rarely slips because of system configuration. Most often it slips because nobody is available to test the documents, the data from the previous program turns out to be in worse shape than assumed, or a decision on how to post a certain transaction waits three weeks. That is why a schedule is best read as a list of tasks for both sides, not just for the contractor.
Typical timelines
According to our price list and our project assumptions so far:
| Scope | Typical duration |
|---|---|
| Pre-implementation analysis | 2 to 5 days |
| One module in a business with up to about 10 workstations | 3 to 6 weeks |
| Standard implementation, 10-20 workstations, one or two modules | 6 to 12 weeks |
| Multi-module environment with production | 3 to 6 months |
| Support after go-live | 30 days |
These timelines run from the start of work, with the availability of people on the company's side agreed in the schedule. We give the exact deadline after the analysis, because only the analysis shows the state of the data and the number of integrations.
Implementation stages
1. Pre-implementation analysis. Workshops with people from the departments that will work in the system. The result is a description of processes, a list of documents, permissions, data to migrate and integrations, plus a schedule with dates for both sides.
2. Configuration and parameterisation. Setting up modules, document definitions, numbering, accounts and permissions. With one module this stage is shorter, provided the decisions from the analysis have been made.
3. Data migration. A trial import, your verification, corrections and the final import. The number of attempts depends on the quality of the source data.
4. Testing. Your staff go through typical scenarios on real data in a test environment: issuing an invoice, approving a document, a payroll, a report. Every problem found goes onto a list with a fix date.
5. Training. Separately for each group, on the configured system, not on a demo version.
6. Go-live and support. Switching work to the new system on an agreed day, followed by 30 days of support included in the implementation price, when questions from day-to-day work come up.
What most often delays an implementation
- No time for people to test. Testing cannot be outsourced to the contractor, because only your staff know what a correct document looks like in their department. That is why we put people's availability into the schedule together with the dates.
- The state of the source data. Duplicate customer and supplier records, missing identifiers and data spread across several spreadsheets lengthen the migration more than any other stage.
- Decisions put off until later. How to post transactions, the approval path for purchase invoices or the split of permissions must be decided before configuration. Every postponed decision comes back as a correction.
- Integrations with other vendors' systems. Their timing also depends on the other side: access to documentation, test accounts and answers to questions.
- KSeF access. Permissions, tokens and certificates must be prepared before go-live, not on the day the first invoice is issued. We describe the details in the post on KSeF in a business.
- Server environment. If the system is to run on premises, the server and backups must be ready before the final migration.
When to choose the go-live date
It is worth setting the go-live date so that one accounting period is not split between two systems, ideally on the first day of a month. The date also depends on your finance team's calendar: going live in the month-end close week or just before the year-end close puts a load on the same people who should be testing the system. We set the exact date together with your accounting team, and if an accounting office keeps your books, with them too.
How to shorten an implementation without shortening the testing
- Name one person on your side who makes decisions and keeps track of deadlines.
- Tidy up the customer, supplier and product records before migration.
- Book your staff's time for testing in the calendar, just like meetings.
- Start with one module if the need is urgent, and add the next ones after a stable go-live.
Where to start
If an ERP implementation is only being considered, start with the questions from the post on when to implement ERP in a business. We describe the cost components in the post on the cost of an enova365 implementation, and the scope, prices and stages of our implementation on the page enova365 implementation. We are an Authorized enova365 Partner.
Sources
- Soneta, enova365: system modules, https://enova.pl/moduly-systemu/ (accessed 10/10/2026)
- Ministry of Finance, KSeF certificates, https://ksef.podatki.gov.pl/informacje-ogolne-ksef-20/certyfikaty-ksef/ (accessed 10/10/2026)
- NexaIT, price list and project assumptions for ERP implementations (as of 10/10/2026), enova365 implementation
As of 10 October 2026.