Getting iplicit implemented correctly matters more than most organisations realise until something goes wrong. Configuration decisions made in the first few weeks shape how the system performs for years. Data migration errors undermine confidence before the finance team has had a chance to get started.
Escone Solutions provides end-to-end iplicit implementation services-from initial scoping through to go-live and the stabilisation period that follows.
Before anything is configured, we spend time understanding your current position. What systems are you running? What does your chart of accounts look like? What are your reporting requirements? Where are the known data quality issues?
This stage produces a clear, agreed scope -including timeline, deliverables, and a risk register. It is also where we identify anything that could affect the project later, so it can be planned for rather than reacted to.
We configure iplicit around your chart of accounts, entity structure, workflows, and approval processes. This is not a template rollout-the system is set up to reflect how your finance team actually works.
Data migration is scoped, mapped, and tested in a staging environment before anything goes live. We agree the scope of historical data with you upfront and run reconciled test migrations before the final cut-over. Find out more: iplicit Migration
Your finance team receives hands-on training using their own data in the configured system. We do not run generic product walkthroughs- training is built around your actual processes, reports, and day-to-day tasks.
User acceptance testing gives your team the opportunity to validate that the system works as expected before go-live. Any issues are logged and resolved before sign-off.
We are available on go-live day and remain closely involved during the settling-in period. Most issues surface in the first two weeks -we prioritise fast resolution during this window and conduct a structured post-go-live review before handover to ongoing support.
Data migration is consistently the part of a finance system implementation that causes the most anxiety-and the most problems when it is not handled well. Getting it wrong means opening balances that do not reconcile and a finance team that loses confidence in the new system before they have properly started.
Our approach:
We will not proceed to go-live if the data does not reconcile. It is always less expensive to delay by a week than to fix a bad migration in production.
A single-entity implementation with a clean data migration typically takes eight to twelve weeks. Multi-entity implementations, complex integrations, or large data volumes take longer. We provide a realistic estimate after the discovery stage — not before, because any estimate given without understanding your specific requirements is not a reliable one.
Implementation is a joint effort. From your organisation we typically need:
We plan around your availability and will not schedule workshops during month-end.
Typically two to four hours per week during active configuration phases, with more time during training and user acceptance testing. We build a project plan around your availability and flag any periods where input is critical well in advance.
Yes. Integrations that are in scope are configured and tested as part of the implementation timeline. Complex integrations may run as a parallel workstream.
Yes, and for many organisations we recommend it. Running parallel gives your team confidence that the new system produces the same outputs as the old one. We help you plan the parallel period and agree the criteria for cutover.
After the stabilisation period, ongoing support transitions to Escone Assist-our dedicated support service for iplicit users. The same team that implemented your system provides your ongoing support. Find out More: iplicit support page
