ERP integrator: what one does, cost, and how to choose

An ERP integrator is the firm that configures your ERP and connects it to the other systems you keep, then stays accountable for that work going live. IBM describes ERP integration as connecting the ERP to other applications, using point-to-point links, an enterprise service bus, or an integration platform as a service. Those methods are the work, and the integrator is the company that owns the result. For a company of about 20 to 100 people on Dynamics 365 Business Central or Odoo, the license is the smaller bill. Business Central Essentials is USD 80 per user per month in the United States as of October 2026, paid yearly, and implementation is a separate purchase.

PCMag defines a systems integrator as an individual or organization that builds a complete solution from diverse components when you want hardware, software, and networking to work across vendors. On an ERP project, that complete solution is configuration, data load, interfaces, testing, and training under one delivery agreement. A reseller can sell the licenses and still pass the build to another firm. Before you sign, ask who employs the people doing the work.

What an ERP integrator is accountable for

Panorama Consulting defines a system integrator as a company that brings hardware and software from multiple vendors together so the components work, and says this role matters on an ERP implementation. That is the job title you are hiring. The technical pattern, whether a direct connection, a service bus, or an iPaaS product, is a design choice inside the job.

For a distributor or a light manufacturer in this size range, the accountable work usually includes five outputs:

1. The ERP is configured for the entities, locations, currencies, and roles you operate.
2. Opening balances, items, customers, vendors, and open documents are loaded from the systems you are leaving.
3. Each system you keep, such as a web store, a payroll tool, a warehouse scanner, or a CRM, has a named interface with a test.
4. Your staff can run order to cash and procure to pay on the new system without re-keying the same order into a spreadsheet.
5. Someone named in the contract is first-line support after go-live.

The public pricing page tells buyers to "Contact a partner to purchase or to get an assessment, consulting services, or additional pricing." The same line appears on the Canadian pricing page. License sale and services are routed through the same door, which is why a reseller can look like the firm that will deliver.

Odoo draws the commercial line differently. Official partners configure the software, set up hosting, and train clients. Odoo does not take a percentage of partner services. Partners set their own service fees, and services are the partner's main revenue. Partners must get Odoo certification, assign dedicated resources, and be first-level support for their clients.

If you already know the platform and you are choosing the firm, read the signs you need a system integrator against your own stack. A single company file with no outside systems is a different project from an ERP that must post orders from a store and send shipments to a 3PL.

Who carries delivery risk: integrator, reseller, or consultant

Three roles show up on proposals. They are not interchangeable, because the signature on the statement of work decides who stays when a data load fails.

• Reseller (often called a VAR) (What they typically sell: Licenses, and sometimes a thin services wrap · Who carries delivery risk: Only the scope written into their services agreement. License margin can be the whole business.)
• ERP integrator (What they typically sell: Configuration, data, interfaces, test, training, and go-live · Who carries delivery risk: The firm that signs the delivery SOW, including work it subcontracts, if the contract says so.)
• Independent consultant (What they typically sell: Selection, requirements, or oversight · Who carries delivery risk: The consultant, only for advice. A person who will not configure or integrate should not be the party signing the build.)

Panorama notes that "many SIs also act as value-added resellers (VARs)". One company can wear both hats. That is workable when the proposal splits the license order from the delivery team, names the consultants, and states their employer. It is a poor deal when the reseller's name is on the quote and an unnamed subcontractor is on the build.

Microsoft's Dynamics 365 implementation guide follows Success by Design stages: Strategize, Initiate, Implement, Prepare, and Operate. The guide is used by the FastTrack team and by partners. It is aimed at medium-sized and larger organizations, points smaller businesses toward Business Central, and tells a business owner to talk to the administrative team and then contact the reselling partner. Read that last step carefully. The reselling partner is the party Microsoft tells you to call, which does not by itself mean that partner's employees will configure your company.

FastTrack for Dynamics 365 gives eligible customers proactive guidance, workshops, checklists, and go-live reviews based on Success by Design. It sits beside the project as guidance, and the implementation firm still does the build. Ask the partner whether your subscription is eligible, and keep FastTrack hours out of the fee you are comparing.

On Odoo, the path depends on headcount. Companies with fewer than 50 employees usually implement directly with Odoo using Success Packs. Mid-size and large companies, meaning more than 50 employees, usually use a partner for local project management. For custom development, Odoo says you can work with Odoo or an official partner. A 30-person company can still hire a local firm. Odoo describes the under-50 path as the usual one, and a local firm remains available when you want one.

The contract test is the same on both platforms. The firm that signs delivery should employ, or explicitly accept liability for, the people who configure, integrate, and train. An advisor who helps you choose the platform and then leaves the SOW to a reseller has not taken that risk.

What the license costs in the US and Canada

Treat the figures below as software only, as of October 2026. They do not include implementation, data migration, or interfaces. US prices come from Microsoft's Business Central pricing page. Canadian prices come from the Canada pricing page and are plus applicable tax.

• Business Central Essentials (United States: USD 80 per user per month, paid yearly · Canada: CAD 108.50 per user per month, paid yearly)
• Business Central Premium (United States: USD 110 per user per month, paid yearly · Canada: CAD 149.20 per user per month, paid yearly)
• Business Central Team Members (United States: USD 8 per user per month, paid yearly · Canada: CAD 10.90 per user per month, paid yearly)

Team Members is a limited license. Do not count a buyer, a warehouse lead, or an accountant as a Team Member until a partner shows that the role's tasks fit that license. Essentials covers the core finance and distribution set for many single-entity firms. Premium is the step up when manufacturing features are in scope. Confirm the edition on your own process list.

Odoo subscriptions are also separate from services. As of October 2026, the Odoo pricing page shows the Standard plan at USD 31.10 per user per month on the yearly display (USD 38.90 shown as the undiscounted monthly figure), for all apps on Odoo Online. The Custom plan is USD 61.00 per user per month on the yearly display (USD 76.20 undiscounted monthly), and it includes Studio, multi-company, and the external API. Odoo.sh hosting is extra on Custom. The yearly discount is valid for 12 months for initial users. A Light User is listed at USD 8.90 and is sold after an advisor reviews requirements. The pricing FAQ states that implementation, meaning project management, needs analysis, data import, customizations, developments, and training, is a separate purchase. For a Canadian company, ask Odoo or the partner for the subscription in CAD before you compare it with the US figures above.

Assume 25 users, of whom 8 need a full Business Central license and 17 can use Team Members after a role check. In the United States, Essentials for those 8 users is USD 640 per month, or USD 7,680 per year. Team Members for the 17 is USD 136 per month, or USD 1,632 per year. The license total is USD 9,312 per year. The same mix in Canada is CAD 868 per month for Essentials (CAD 10,416 per year) plus CAD 185.30 per month for Team Members (CAD 2,223.60 per year), or CAD 12,639.60 per year before tax.

Assume the same 25 people on Odoo Standard at the yearly display price. The subscription is USD 777.50 per month, or USD 9,330 per year, and that figure still excludes implementation. If 8 of them need the Custom plan because you require multi-company or the external API, recompute from the Custom price for those 8 and keep Standard only where the advisor agrees. Light User pricing should wait for that review.

A year of licenses near USD 9,300 is a real bill. It is still the smaller bill once configuration, history, and two or three interfaces enter the scope.

What implementation prices are published

Take the day rate from the bidder's quote. Odoo states that partners usually charge for their services per day of consulting or development. Ask for that rate in writing, with the name and employer of each consultant.

What Odoo does publish is its own Success Packs: prepaid blocks of a dedicated Odoo consultant's time. These are Odoo staff, not a quote from a US or Canadian partner. New-customer prices include 15% off the first pack, as of October 2026, from the Success Packs page.

• Starter (Hours: 4 · New-customer price: USD 493 · Returning-customer price: USD 580)
• Basic (Hours: 25 · New-customer price: USD 3,060 · Returning-customer price: USD 3,600)
• Standard (Hours: 50 · New-customer price: USD 5,950 · Returning-customer price: USD 7,000)
• Custom (Hours: 100 · New-customer price: USD 10,625 · Returning-customer price: USD 12,500)
• Pro (Hours: 200 · New-customer price: USD 21,250 · Returning-customer price: USD 25,000)

On those new-customer prices, the Standard pack works out to USD 119 per hour of the block, and the Pro pack works out to USD 106.25 per hour. That arithmetic describes the pack. It is not a local firm day rate. The Standard pack is the tier that includes data-import assistance. The Custom pack includes customizations, and extra monthly charges apply for maintenance of extra modules or lines of code. Onsite consulting is not in every pack. Travel time and travel expenses are billed separately.

Odoo says 80% of projects in the estimator's illustrated scope go to production in 200 hours or less. A minimum 50-hour Success Pack is required before Odoo will analyze performance issues. Both points are Odoo delivery terms, and they are separate: the first is how long that illustrated scope takes to reach production, and the second is the smallest pack Odoo requires before it will look at performance. If you need local project management or interfaces outside that illustrated scope, you are in partner territory even when headcount is under 50.

The "What if I have custom needs that require developments and ad hoc integration?" question on that page is the fork. Custom work can stay with Odoo or move to an official partner. Either way, get three lines: the build hours, the maintenance charge on custom modules or code, and who owns the result if you change firms later.

Odoo also publishes what a firm pays Odoo to be in the partner program. The Learning tier is USD 990. The fee listed to discuss Ready, Silver, or Gold is USD 3,950. Those are partner program fees, not your project fee. A tier tells you the firm joined a program and took on duties such as certification and first-level support. It does not tell you the day rate, the team on your account, or whether the references match your industry. Ask for reference counts, typical project size, and the names of certified people on the proposal. Weigh the tier only after those answers are in writing.

What a selection budget per user includes

Software Path's 2020 to 2025 ERP project report, drawn from 10,000 selection projects, puts the average budget at USD 8,528 per user. The same page gives cloud projects USD 10,500 per user, installed projects USD 6,000 per user, and projects with no hosting preference USD 8,500 per user. It says cloud buyers usually budget more fully for implementation and first-year services. Industry figures on that page include healthcare at USD 13,000 per user, oil and gas at USD 12,500, and retail at USD 7,500. This is a selection-project budget. It mixes software and services. It is not an integrator's fee schedule.

Using the average on the 25-user company above is a planning envelope of USD 213,200 (25 times USD 8,528). The cloud figure on the same page is USD 262,500. The installed figure is USD 150,000. Retail's USD 7,500 per user would be USD 187,500. None of those numbers is a bid. They are useful when a proposal's all-in year-one number is a small multiple of the USD 9,312 license example and the proposal still claims to include data, interfaces, and training. Something in that proposal is probably excluded.

The same Software Path summary says average ERP selection time across all businesses is 18 weeks, up 3 weeks since the start of the data period. Cloud preference rose from 56.2% in 2020 to 63.3% in 2025, and the share of buyers with 0 to 49 employees rose from 42.2% to 46.6%. Buyers in that dataset asked for comparisons (39.2%), pricing (27.8%), and selection guides (16.5%). If you have already picked Business Central or Odoo, you can skip most of those 18 weeks. You still need the pricing clarity they were hunting: license, services, and data as separate lines.

An older rule of thumb, at least one dollar of services for every dollar of software, is described on Top10ERP's implementation cost page as a past SMB habit. Cindy Jutras writes there that subscription pricing and easier configuration have made that ratio less predictable. She does not give a new ratio. Budget services from hours, packs, or a phased statement of work, on their own lines.

What discovery should produce before a build fee

Discovery is the paid work that makes a fixed fee match the scope. A proposal that jumps from a demo to a build price is guessing at your data and your interfaces. Ask for these artifacts before you authorize the build:

1. A process map for order to cash, procure to pay, and inventory, marked with who does each step today.
2. An integration inventory: every system that stays, what it sends, what it receives, and whether the pattern is point-to-point, a bus, or an iPaaS. Our guide to ERP integration patterns is a useful checklist for that inventory.
3. A keep-or-replace note for each outside system. IBM's integration overview uses CRM, commerce, and HR as typical connections. Some of those belong inside Business Central or Odoo. Some should stay where they are. Write the choice down so phase one does not silently include a storefront rebuild.
4. A data-cleansing scope: which files, which fields, who cleans them, and how many open documents move.
5. Named consultants, their employer, and the hours each role is expected to spend.
6. A written statement of who employs the people doing the work, including subcontractors, and who you call when a defect shows up after go-live.
7. A phase plan that states what is usable at the end of phase one, and what is deferred.

Top10ERP's integration FAQ estimates that simple point-to-point integrations take 2 to 6 weeks per connection, iPaaS work for 5 to 10 systems takes 2 to 4 months, and complex middleware integrations take 6 to 12 months, with extra time for data cleansing, testing, and training. The same FAQ says the biggest mistake is underestimating data quality and advises planning 20 to 30% of the integration budget for cleansing and validation. Those are that publisher's estimates, not a measured study. Use them to challenge a timeline. A quote that connects five outside systems in three weeks has not left room for the data work that FAQ flags.

Our target for a first usable phase is 8 to 12 weeks, using the Flectic Accelerated Delivery Framework, for a scope that has already survived this discovery list. That target is ours. It is not a market average, and it assumes the integration inventory is short enough to fit the phase.

The "Can I integrate my ERP system myself, or do I need a consultant?" question has a practical answer. A team that already knows both products can own one clean connection on a 2 to 6 week pattern. Configuration of the ERP, a dirty item master, and training for 25 people are a different project. Put the firm on the delivery agreement when a missed go-live stops shipping.

If you are still weighing whether a process should move into the ERP or stay integrated, run the stack through our ERP comparison, then make the keep-or-replace list with the integrator.

What to reject in a proposal

A weak proposal fails in predictable places. Reject or rewrite these before you pay a build invoice.

1. The seller is mainly a license reseller, and the people who will configure the system are not named. Ask for the employment statement. If the answer is a different company, the SOW should say the firm you pay is responsible for that company's work.
2. A fixed fee that excludes data migration, custom code, travel, or interface testing. Those are the lines that arrive later as change orders. Odoo already bills travel outside the pack when onsite work happens. A partner quote should be at least as explicit.
3. A Gold, Silver, Ready, or Solutions badge offered in place of references in your industry. Duties such as certification and first-level support are real on the Odoo partnership terms. They do not replace a call with a company of your size that went live on similar workflows.
4. FastTrack, or an Odoo Success Pack, described as the implementation. FastTrack is guidance for eligible customers. A Success Pack is a block of Odoo consultant hours with a published ceiling. Neither one is a local team that knows your warehouse.
5. Custom code is missing an owner and a maintenance charge. The Custom Success Pack warns that extra monthly charges apply for extra modules or lines of code. A partner build needs the same sentence in your contract.
6. A single calendar that ignores data. If the publisher estimate of 20 to 30% of integration budget for cleansing is even roughly relevant, a plan with zero hours for cleansing is incomplete.

You can compare two integrators on the same grid: named people, hours by phase, references you can call, a phase plan with a usable end state, and code ownership. Price is the output of that grid.

What to do after you pick the platform

You do not need another 18-week selection if the platform is already chosen. You need a firm that will price the work the license page left out.

Start with an internal list: users by role, systems that stay, files that are dirty, and the date after which the old system cannot run another close. Bring that list to two conversations at most. One can be the vendor path (a Business Central partner assessment, or an Odoo Success Pack if you are under 50 employees and the scope fits the illustrated packs). The other should be a firm that will sign delivery, name its consultants, and phase the work.

How to choose an ERP implementation partner goes further on references and contract structure. For the connection work itself, our system integration service is the engagement that covers interfaces, test, and the cutover between Business Central or Odoo and the applications you keep. Broader configuration, data migration, and training sit in ERP implementation, phased so the first release is something the warehouse and the finance team can run.

Ask each bidder to price data migration as its own line, interfaces as their own line, and travel as its own line. Ask who employs every person on the build. Ask what you will be able to do on the Monday after go-live, and what will wait. The firm that answers those questions in writing is the integrator. The firm that answers with a license total and a badge is still a reseller.

How Flectic can help

Flectic connects your Odoo or Dynamics 365 system to the store, payment, payroll, carrier and reporting tools you keep, and stays accountable for each flow. Every integration runs through the five delivery stages, and each flow gets an owner and a documented failure path before it carries real data. To see how that work is scoped, read Flectic's system integration service. To start, book a free discovery call.

Sources

Definition of systems integrator, PCMag, October 2026.

What is a System Integrator?, Panorama Consulting Group, October 2026.

What is ERP integration?, IBM, October 2026.

Dynamics 365 Business Central pricing (United States), Microsoft, October 2026.

Dynamics 365 Business Central pricing (Canada), Microsoft, October 2026.

FastTrack for Dynamics 365, Microsoft, October 2026.

What is the Dynamics 365 implementation guide?, Microsoft Learn, October 2026.

Odoo partnership, Odoo, October 2026.

Odoo pricing, Odoo, October 2026.

Odoo Success Packs, Odoo, October 2026.

2020 to 2025 ERP software project report, Software Path, October 2026.

What is ERP Integration?, Top10ERP, October 2026.

ERP implementation costs, Top10ERP, October 2026.