Skip to content
BigTree108

ERP implementation and development

ERP implementation and development services for Microsoft Dynamics 365, SAP S/4HANA, Oracle Fusion Cloud ERP and E-Business Suite, Oracle NetSuite, Odoo and Acumatica: discovery, fit-gap, configuration, customisation, integrations, data conversion, testing, training, go-live and support for manufacturing, distribution, retail, professional services and finance, with dedicated ERP developers and consultants for your team or a project delivered end to end, and our own .NET, Python, front-end and QA engineers for the services, portals and tests around the ERP.

ERP platforms we work on

Each page covers what we build on the platform, the ways to work with us and the questions clients ask first.

The work we take on

  • ERP implementation

    Fit-gap workshops, configuration, data loads, user training and go-live support, for a first ERP or a rollout to further companies and countries.

  • ERP customisation

    Code that adds what the standard product lacks, written with the vendor’s extension model so the next upgrade installs without anyone undoing it.

  • ERP integrations

    Payroll, banks, e-commerce, CRM, EDI, document management and your own systems, connected through the platform’s APIs with retries, dead-lettering and alerts on both ends.

  • ERP support

    Incidents, change requests and month-end support under agreed response times, from the same people every month, with each vendor update tested before it reaches production.

  • ERP data migration

    Extraction, cleansing, mapping and repeatable loads from the system being retired, with a reconciliation report for every migrated object rather than one cut-over spreadsheet.

  • ERP upgrades

    ECC to S/4HANA, NAV and GP to Business Central, AX to Finance and Operations, E-Business Suite to Oracle Fusion, and Odoo and Acumatica from release to release, with custom code reworked and every step rehearsed on a copy first.

  • ERP reports and dashboards

    The reports the standard product does not ship, in the platform’s own analytics or in Power BI when the people reading them live in Microsoft 365.

  • ERP test automation

    Regression suites for the screens, the integrations and the month-end runs, executed before every release so a broken posting rule is found by a test rather than by finance.

  • Portals and apps around the ERP

    Customer, supplier and employee portals and mobile apps that read and write ERP data, built by our .NET, front-end and mobile engineers.

How an ERP implementation runs

  1. Discovery and plan

    Workshops with finance, HR, operations and IT to map today’s processes, reports and interfaces, ending in a scope, a phased plan with finance usually live first, named people on both sides and the effort your own staff will need.

  2. Requirements and fit-gap

    Every requirement traced to standard configuration, an extension, an integration or a report, with gaps closed by configuration first and code only where configuration cannot, in a solution design you approve.

  3. Configuration and extensions

    The system built in development and test environments, extensions written with the vendor’s extension model and kept in source control, and every change promoted through test before it reaches production.

  4. Data conversion

    Master data, open items and the years of history you choose extracted from the old system, cleansed and loaded by repeatable scripts, rehearsed in several mock conversions and reconciled object by object with finance.

  5. Integrations and reports

    Banks, payroll, tax, procurement, document management and your own systems connected through the platform’s APIs, and the statutory, management and audit reports rebuilt and checked against the old system.

  6. Testing

    Functional, integration and user acceptance testing against scripts written from your processes, parallel payroll runs compared line by line before payroll moves, and regression suites kept for every later update.

  7. Training

    Train-the-trainer sessions for key users, role-based courses and guides written for your configuration rather than the vendor’s demo, so your own people carry the system after go-live.

  8. Go-live and hypercare

    A cut-over plan rehearsed end to end, a go or no-go decision on agreed criteria, and the project team on hand through the first month-end and year-end close.

  9. Support and releases

    Incidents and change requests under agreed response times, each vendor release tested before it reaches production, and your data handed back in open formats whenever you ask for it.

How we work on an ERP programme

We take the whole programme or any part of it. We can run the implementation, upgrade or rollout as the team that owns the plan, or join the programme your implementation partner or in-house team runs and take the build, integration, migration, reporting and test work inside their method, environments and ticket queue.

Licences come from the vendor or your licensing partner. Production data stays where your rules say it stays: development, migration rehearsals and testing run on non-production systems with masked data unless you decide otherwise, through your accounts and your access controls.

The ERP problems we already live with

We run our own company on a platform we built: hiring, onboarding, contracts, time tracking, leave, compensation and invoicing, on .NET, Angular and Azure. It is not an ERP product, but it has the problems an ERP programme has: one source for every figure, approvals that leave an audit trail, payroll inputs that must reconcile with invoices, and personal data that only the right people can read. Read the case study.

Questions about ERP development

Can you implement the ERP, or work beside our implementation partner?

Both. We can deliver the implementation as the team that owns the plan, or work beside the partner or in-house team that owns the process design, inside their method, environments and ticket queue, so the programme gets more hands without a second design authority.

Which industries do you do ERP work for?

Mostly manufacturing, energy and agriculture, with production and costing; retail and e-commerce, with stores and web shops; wholesale, distribution and logistics, with stock and delivery; professional services, with projects and billing; finance, with accounting and approvals; and hospitality, with point of sale.

Our ERP is not on your list. Can you still help?

Yes. We take on any ERP, including Workday, Infor, Epicor, IFS, Sage, SAP Business One and systems built in-house. Specialists in that platform join your project, and the integrations, reports, data migration and portals around the ERP are built by our own .NET, Python and front-end engineers.

Do your people need access to production data?

Not by default. Build, migration rehearsals and testing run on non-production systems with masked or synthetic data. If you decide someone needs production access, it is granted through your accounts and your access controls, logged on your side, and removed when the task ends.

How is ERP work contracted and billed?

The same way as the rest of our work: one agreement with BIG TREE 108 LLC, a company in the Ukrainian state register, and one invoice a month. Time is logged in our own portal throughout the month and the same figures produce the invoice, so the hours you approve and the hours you pay for are one set of numbers.

Who owns the extensions and integrations you build?

You do. Every specialist has a signed contract with BigTree108 that assigns all work product to the company, and our agreement with you assigns it onward. Code, designs and documents are delivered into your own repositories and tools, not kept where only we can change them.

Running an ERP programme?

Tell us the platform, the work and the dates. You get an answer within one business day: candidate profiles or a plan for the work.