top of page



EIS is Acumatica's premier integration specialist.  Whether you are looking to integrate a custom, homegrown, specialized, or commercial application with Acumatica, EIS builds configurable, manageable, and upgradable integrations using our AcuSync Integration Platform.

"We know integration!  It's our specialty.  All of customers have integrations that we helped them build and configure using our AcuSync Integration Platform."

- Art Ardolino, EIS VP Services


4D Integration Methodology


During discovery, we meet with your staff to identify the desired outcomes of the integration.  We examine the different integration options available (APIs, files, etc.), and create screen-by-screen mappings to align the data between the systems both at a record and field level.  We also establish point of entry and ownership for each record type and field.  We determine which data elements should be exchanged between systems and in which direction.  We document all the business requirements of the integration.

Desk Computer Screens


During design, our architects take the integration business requirements, mappings, and desired outcomes and analyze the technology available to achieve the desired integration.  This becomes a functional design document that indicates how the integration should be configured using our AcuSync Integration Platform.  If connecting to a system new to AcuSync, a design for a new AcuSync Data Provider is also created, ensuring that the integration design is configurable, manageable, and upgradable.



During development, the AcuSync Data Provider is built (if necessary) and the functional mappings are configured as AcuSync Import and Export Scenarios.  The advanced features of AcuSync are used to align and transform the data between Acumatica and the system being integrated.  As each Import/Export Scenario is created, they are tested to ensure that data is flowing between the systems as desired.

At Work


During delivery, the completed integration is presented for user acceptance testing in a sandbox environment.  Test cases are established.  Integrations are tested manually and then automation schedules are created to incrementally move data in real-time.  Once testing is complete, a deployment strategy is created for production, which may include an initial synchronization of data between systems before enabling the integration.  Users are trained how to use AcuSync to monitor and maintain the integration.

Female Developers

"We decided to build AcuSync because we needed a way to build new integrations at scale that are both configurable and upgradable.  We can now connect Acumatica to new systems in just a few weeks."

- Jeremy Hornback, EIS Chief Technology Officer

bottom of page