Connecting Cadmium and A2Z for the U.S. Naval Institute

Event technology often depends on several platforms working together.

For the U.S. Naval Institute (USNI) and AFCEA International, Cadmium manages session and speaker information for the West Conference, while A2Z supports the conference website and mobile app. AMS Geek is using Data Sangria to build a one-way integration between the two systems.

The goal is simple: reduce spreadsheet imports and duplicate data entry while keeping event information up to date through the conference.

Creating a Clear Path for Event Data

For this integration, Cadmium remains the source for accepted session and speaker information.

Once the team approves information in Cadmium, Data Sangria will move that information into A2Z. As a result, A2Z can use the latest approved data on the West Conference website and mobile app.

Data Sangria serves as the connection between the two platforms. Its integration microservices will sync the event information that both systems need.

That creates a much clearer process:

Manage the information in Cadmium. Approve it there. Then let Data Sangria move it where it needs to go.

Keeping Speaker and Session Information in Sync

The integration will handle several important parts of the West Conference program.

First, it will create or update contacts and sessions in A2Z. It will also connect speakers to the correct sessions, assign the right speaker roles, and match tracks with the appropriate sessions.

In addition, Data Sangria will transfer speaker details such as names, credentials, titles, companies, and biographies.

For sessions, it will sync information such as titles, learning objectives, dates, times, rooms, descriptions, status values, and track assignments. The integration can also transfer sponsor data when the necessary source information is available.

Together, these connections help keep important program information aligned across both platforms.

Keeping Up With Event Changes

Of course, event information rarely stays the same from planning through conference day.

Speakers change. Sessions move. Details get updated. Sometimes sessions get canceled entirely.

Because of that, the integration will process both new and changed records. It will also handle speaker removals and session cancellations. At the same time, repeated syncs will avoid creating duplicate records.

As a result, the event team can spend less time exporting and importing spreadsheets every time something changes.

Instead, Data Sangria creates a consistent flow between the two systems.

Moving the Right Data at the Right Time

A useful integration should do more than move information. It should also follow the organization’s rules for that information.

For example, only approved Cadmium records will move into A2Z. Hidden or incomplete records will stay out of A2Z unless the team approves a rule that allows them to publish.

The integration will also use approved mappings for session types, tracks, and speaker roles. If it finds an unknown controlled value, it will return a clear error rather than sending uncertain information forward.

Additionally, Data Sangria will clean unsupported HTML when necessary and follow A2Z field-length limits. Just as importantly, the integration will leave unrelated A2Z event information alone.

These rules give the team more control over what moves between the systems and help create a more reliable sync.

Connecting the Systems You Already Use

This project shows why integration does not always mean replacing technology.

Cadmium already has a clear role in managing session and speaker information. Likewise, A2Z has a clear role in delivering that information through the conference website and mobile app.

So instead of asking one platform to do everything, Data Sangria connects the two.

That connection gives information a clear path from the system where staff manage it to the system where attendees need to see it.

Ultimately, that means fewer manual imports, less duplicate data entry, and less time spent keeping two platforms aligned.

That is what good integration should do: help the systems you already rely on work better together.