Fortis Payment Systems · Embedded payments and merchant services (US)

How Fortis moved a sales team off Salesforce and runs merchant boarding from HubSpot.

Fortis Payment Systems is a US embedded payments provider. After it acquired Serve First Solutions, whose sales team ran on a heavily customised Salesforce, we migrated that team’s active data into Fortis’s HubSpot and ran the cutover over a single weekend, so reps were back in HubSpot on Monday morning with their full history. We also built a custom two-way integration with Fortis’s Partner API, so reps pick an office and agent and submit merchant boarding applications from the deal. Salesforce is retired, and every closed-won deal carries an office ID and an agent ID.

600,000+
contacts migrated, with leads, companies, deals, activities and the Terminals object
1 weekend
production cutover: out of Salesforce on Friday, back in HubSpot on Monday with full history
34%
increase in deal throughput reported by Fortis following the migration and the move to one process

The challenge

Fortis’s HubSpot had grown across many teams, and then the business acquired Serve First Solutions, which ran on its own Salesforce. Fortis needed everyone on one platform without stopping sales.

  • A non-standard source system. Serve First’s Salesforce had custom objects, an unusual lead-to-opportunity structure, a custom Terminals object and separate credit card and ACH pipelines. It had to be retired, with its active data moved intact.
  • A HubSpot portal with no common process. Twenty-four teams worked to their own processes, and 749 workflows had no folder structure and almost none had a recorded owner. An audit found real working parts alongside broken ones.
  • A sales team that couldn’t stop selling. The plan was to stop working in Salesforce on Friday and carry on in HubSpot on Monday, with context intact.
  • Boarding steps done by hand. Reps looked up office and agent IDs in a separate system, classified each merchant’s business type manually and submitted boarding applications outside HubSpot. In a regulated process, that adds delay and room for data-entry errors.

What we built

We worked in a deliberate order: stabilise the existing HubSpot first, get reps onto one way of working, build the integration Fortis needed, then migrate Serve First’s data once the target was in a known state. The project had five parts.

  1. 01

    Audit and stabilise

    We audited the portal and tidied its governance before any migration work began, rather than layering new structure on top of the old.

    • HubSpot
  2. 02

    One way of working

    A single pipeline and process replaced the team-specific ones. We piloted it with 13 reps on live merchant records, then rolled it out to the wider sales team of around 100, with in-app guidance at each deal stage and on-site training for Serve First before go-live.

    • HubSpot
    • Supered
  3. 03

    A custom integration with Fortis’s Partner API

    Reps choose an office and agent on the deal and submit the boarding application from there. A new Agents object in HubSpot records each confirmed selection and its status.

    • HubSpot
    • Fortis Partner API
  4. 04

    A staged migration

    After a test run, we moved more than 600,000 contacts, along with leads, companies, deals, activities and the Terminals object into the two pipelines. The production cutover ran over one weekend.

    • Salesforce
    • HubSpot
  5. 05

    Cleanup and retirement

    We migrated file attachments through a custom API, reassigned records still tied to former Serve First users, and retired Salesforce with no dependency left on it.

    • Custom API
    • HubSpot
Why we built it this way

A standard HubSpot workflow action can read and write properties, but it can’t show an interactive lookup inside a deal or hold a multi-step selection of office, then agent, then confirm. So the integration is a card in the deal record that calls a function running on HubSpot’s servers. Reps get a proper lookup-and-confirm step, and the code that talks to Fortis stays server-side, with credentials held as secrets rather than written into the code.

On the migration side, standard tooling doesn’t reliably carry file attachments, so we built a custom API for them. We also audited Serve First’s unusual Salesforce structure before moving anything, rather than discovering its quirks halfway through.

How the boarding integration works

Reps find the office and pick the agent on a card inside the deal. They confirm, we check the deal has everything the application needs, and HubSpot creates an Agents record and submits the application to Fortis. Fortis’s response is saved back on that record. Business category and type are set on the deal through cascading dropdowns built from Fortis’s own reference data.

One confirmation on the deal submits the application to Fortis Category and type On the deal, from Fortis data 1  Find the office In HubSpot: deal card search Behind it: Fortis offices API 2  Pick the agent In HubSpot: agent list on card Behind it: Fortis agents API 3  Confirm and check In HubSpot: confirm on the card Behind it: contact and company 4  Create Agents record In HubSpot: linked to the deal Behind it: custom Agents object 5  Submit to Fortis In HubSpot: tagged with deal ID Behind it: Fortis Partner API 6  Save the result In HubSpot: Agents record Behind it: Fortis ID and status
  1. 1  Find the officeIn HubSpot: deal card searchBehind it: Fortis offices API
  2. 2  Pick the agentIn HubSpot: agent list on cardBehind it: Fortis agents API
  3. Category and typeOn the deal, from Fortis data
  4. 3  Confirm and checkIn HubSpot: confirm on the cardBehind it: contact and company
  5. 4  Create Agents recordIn HubSpot: linked to the dealBehind it: custom Agents object
  6. 5  Submit to FortisIn HubSpot: tagged with deal IDBehind it: Fortis Partner API
  7. 6  Save the resultIn HubSpot: Agents recordBehind it: Fortis ID and status

Read left to right, then along the second row. Each step happens on the deal, with the connected tool named beneath it. A daily sync also keeps the Fortis employee responsible for each deal up to date.

The details that made it work

A simple link turned into a full application

We first assumed we could send Fortis a light update saying a deal belongs to a particular agent. Fortis’s API specification has no such call. The only way to write anything about agents is to create a full merchant application. So we reframed the write-back as application submission, and pull the signer, business and company details from HubSpot instead of asking reps to re-enter them. One confirmation now does the whole job, and the application is tagged with its HubSpot deal and Agents record so it can be traced back.

Example with illustrative values

Live search stopped working at real volumes

Searching Fortis’s offices as reps typed worked in testing. At production volumes, with more than 1,400 office IDs, it stopped working well because of how the API paginates results. We moved to a lookup list that refreshes daily, trading up-to-the-minute freshness for reliability at that scale. Reps search the list by name or ID.

Standard tooling doesn’t carry attachments

Serve First’s records held around 40,000 file attachments, and standard migration tooling doesn’t reliably move them. Rather than accept gaps, we built a custom API to carry them across. All 40,000 files arrived with their original filenames, each matched back to the right record.

Rehearsed first, cleaned up after

Before the production cutover we ran a test migration on a representative set of records, checking data accuracy, field mapping and what showed on each record’s timeline. Fortis reviewed a written test summary before we went ahead, and we switched off workflows and emails in the migration environment so nothing fired by accident. After cutover we found more than 60,000 contacts and over 200,000 tasks still assigned to former Serve First users, and worked with Fortis’s operations team to reassign them to current owners.

How we delivered it, and keep it running

  1. Phase 1Audit and agreed migration rules: open leads and opportunities in, closed-won out, an activity cutoff set with sales leadership
  2. Phase 2The integration build
  3. Phase 3Go-live and training
  4. Phase 4Migration and cleanup

We built the integration in a sandbox and demoed it to Fortis’s technical business analyst, who validated it before it went live. For the migration, Fortis named a stakeholder for acceptance testing and sign-off, and the head of Serve First joined architecture discovery and confirmed cutover readiness. We held weekly working syncs during active build, easing to every other week once things were stable, and reviewed each phase with Fortis leadership after it went live before starting the next.

Built to keep running

  • Checks before anything is written. The integration checks every required detail and stops with a list of exactly what is missing before it writes to HubSpot or Fortis.
  • Failing in the open. The Agents record is created before the application goes to Fortis. If Fortis rejects it, the function returns Fortis’s exact error and the ID of the record already created, so the rep, and any error monitoring, can see what did and didn’t happen.
  • Daily refresh. The office list and the responsible Fortis employee refresh every day, and historical records are kept.
  • Credentials out of the code. Fortis uses fixed keys rather than refreshable tokens, so nothing expires automatically. Rotation is a process outside the code.
  • Support after go-live. A full search outage was fixed the day it was reported, and a display problem after a HubSpot platform update within 24 hours. We have kept extending the integration with name labels, search by office ID and the write-back, and onboarded Contego Group, another Fortis business unit, on the same lookup framework.

The results

Serve First’s sales team
They returned to HubSpot with their full history. 40,000 attachments are matched to the right records, and more than 60,000 contacts and 200,000 tasks have been reassigned to current owners.
Sales reps
Offices and agents are chosen inside the deal they are already working in, with no separate system and no copying of IDs. Every closed-won deal has an office ID and an agent ID.
Sales leadership
Fortis reports deal throughput up 34% following the migration and the move from 24 team processes to one. The pilot of 13 reps grew into full rollout across the sales team, and HubSpot’s own customer success manager scored Fortis’s overall usage at 70 out of 100.
Underwriting
Business category and type come from Fortis’s own reference data, so the classification matches Fortis’s system rather than being typed by a rep.
Revenue operations
Salesforce is fully retired. Boarding status is stored on the Agents record, so applications can be reported by status or office without opening Fortis.
Operations
Every application arrives at Fortis tagged with its HubSpot deal ID and record ID, so it can be traced back to where it started.
Marketing and other business units
Contego Group was onboarded onto the same framework, and Fortis’s marketing team has picked up HubSpot’s AI Prospecting Agent on its own.

Fortis now runs sales on one platform, with a two-way link to its own systems that is carrying new business units.