Service

System integrations

Connect your modern website or portal to the systems that already run your agency — without ripping them out.

Discuss an integration Systems we connect

The reality

Your data lives in 14 different places. We bridge them.

Most agencies have a permitting system, a tax system, a GIS, a CRM, a financial system, and a document repository — each from a different vendor, each with its own API or lack thereof. We build the integration layer that lets your new portal talk to all of them.

Common Systems

Systems we integrate with

Permitting & licensing

Tyler EnerGov, Accela, OpenGov Permitting, and custom legacy systems.

Tax & revenue

Tyler Munis, CentralSquare, Springbrook, and state tax systems.

GIS

Esri ArcGIS Online, ArcGIS Enterprise, and OpenStreetMap-based stacks.

Payment processors

Stripe, Authorize.net, Heartland, NIC, GovOS, Point & Pay, and PayGov.

Identity & SSO

Okta, Microsoft Entra ID, Google Workspace, Login.gov, and state identity providers.

Records & documents

OnBase, Laserfiche, SharePoint, and standalone document stores.

CRM & case management

Salesforce Public Sector, Microsoft Dynamics 365, and home-grown systems.

Financial & ERP

Oracle, SAP, Workday, and mid-market public-sector ERP suites.

Legacy & mainframe

Yes, even those. SOAP, fixed-width files, scheduled SFTP — we can work with them.

How we build integrations

Clean, observable, replaceable

API gateway

A single, documented API gateway in front of your systems — with rate limiting, auth, and logging.

Async & resilient

Queued jobs and retry logic so a 30-second mainframe call doesn’t freeze the resident’s browser.

Observable

Every integration call is logged and graphed. You see error rates and latency in real time.

Who it’s for

Agencies whose systems do not talk to each other

This fits an agency launching a new website or portal that needs live data from existing systems. It also fits IT teams tired of nightly exports, manual re-keying and old scripts no one documented. The IT director or a department’s systems lead usually owns the work.

The problems are familiar. Staff copy data between systems by hand. A resident pays online, but the tax system does not know until the next batch runs. A vendor upgrade breaks a script, and no one finds out until residents call.

What your agency provides

A list of the systems involved and who owns each
API documentation, file layouts or vendor contacts
Test environments or sample data for each system
Your rules for service accounts and credentials
Staff who can confirm the data looks right

The process

How an integration project runs

1

Discovery and scoping

We list every system, data flow and owner, and test what each system can do. You get a written scope.
2

Design and architecture

We design the gateway, data mappings and error handling, and document each connection.
3

Build and iterate

We build one connection at a time in two-week sprints, against test systems first.
4

Test, train and launch

Your staff check real records end to end. We switch to production with a runbook and walk IT through the logs.
5

Hypercare and transition

We watch error rates closely after launch, then hand off to maintenance or your IT team.

These are the same phases we use on every project. The full plan is on our implementation page.

Related work

How it fits with our other services

Portals rely on integrations, so that when residents apply and pay, your back-office systems update.
Your content management system can show live data such as permit status or GIS layers.
The integration layer can run on our managed hosting, with the same monitoring and logs.
A maintenance contract keeps connections working when vendors upgrade their systems.

Every service is listed on our capabilities statement. To map your systems with us, start on our contact page.

FAQ

Questions about integrations

How do we buy integration work?

As part of a larger project or on its own. We respond to RFPs and work under cooperative purchasing agreements, with fixed-fee pricing tied to deliverables. You keep the systems you have.

How long does an integration take?

It depends on the systems and how well they are documented. A modern API connects faster than a mainframe file feed. The written scope sets a date for each phase.

Who owns the integration code?

The statement of work sets ownership of the code before work starts. Every connection is documented, so your team or another vendor can maintain it.

Do integrations affect accessibility?

The integration layer has no screens of its own. Pages and portals that show its data are built to WCAG 2.2 AA, including the messages shown when a system is down.

What happens when a vendor changes its system?

Monitoring flags failed calls as they happen. Under a maintenance contract, we update the connection and test it again.

Related Services

Let’s talk about your project

Tell us what you’re trying to accomplish and we’ll respond within one business day with next steps.

Request a consultation See all government services