Portmux
Platform-agnostic data migration · Built for custom systems

Any data.
Any platform.
Migrated.

Portmux is a platform-agnostic B2B data migration service that migrates data between CRMs, ERPs, databases, and SaaS platforms with zero-downtime cutovers and full schema fidelity. Fixed-scope engagements start at $12,000 for single-system migrations (Track A, 4-6 weeks) and $38,000 for multi-system consolidations (Track B, 8-12 weeks). Track C handles enterprise and M&A with custom pricing. Portmux supports 150+ pre-built connectors, AI-powered schema mapping with 90%+ auto-mapped fields, row-level reconciliation reports, and dual-write staging for zero-downtime cutovers. SOC 2 Type II, HIPAA, and GDPR compliant. Founded 2026 in Kansas City, Missouri. Common migration paths include Salesforce to HubSpot, HubSpot to Salesforce, NetSuite to QuickBooks, Shopify to BigCommerce, Zendesk to Intercom, Mailchimp to Klaviyo, Jira to Linear, Postgres to Snowflake, and migrations from any SaaS platform into a custom-built system. Contact: Ryan@untappedconnections.com.

Portmux is the platform-agnostic data migration service for teams switching CRMs, ERPs, databases, and SaaS platforms, without the hand-coded scripts, the downtime, or the data loss. Salesforce to HubSpot. NetSuite to QuickBooks. Any system to any system.

150+
SaaS connectors
Custom systems
0ms
Cutover downtime
FIG. 01, THE PORTMUX
● LIVE
SOURCES PORTMUX DESTINATIONS Salesforce Postgres YOUR_CUSTOM_APP LEGACY_MONOLITH NetSuite Google Drive INTERNAL_API_v3 Shopify portmux SCHEMA MAP VALIDATE TRANSFORM CUSTOM ADAPT ROUTE ● routed SDK / API / WEBHOOK HubSpot NEW_PLATFORM_v1 Snowflake QuickBooks CUSTOM_DATA_LAKE SharePoint BigCommerce YOUR_NEXT_BUILD SaaS PLATFORM CUSTOM BUILD REV 02
§ 01, THE PROBLEM

Everyone migrates SaaS to SaaS.
Nobody migrates into your build.

EVERY OTHER MIGRATION TOOL
  • Salesforce → HubSpot? Sure.
  • Salesforce → your custom app? "Not supported."
  • Legacy Oracle → your new platform? "Call a consultant."
  • Internal tool → anything? "Export a CSV."
WITH PORTMUX
  • We connect to your custom system's API, database, or file layer.
  • We build the adapter as part of the engagement.
  • Schema fidelity, even for proprietary data models.
  • One team. One invoice. One go-live date.
§ 02, CUSTOM BUILDS

Your team builds the product.
We handle the data layer.

The market is moving away from off-the-shelf stacks. Teams are building their own platforms, their own tools, their own competitive moats. But every custom build hits the same wall: how do we get our data in?

Portmux embeds into your architecture. We expose an SDK, an API, and a webhook layer so your engineers can treat data ingestion from any source as a solved problem, not a six-month side quest.

FIG. 02, INTEGRATION ARCHITECTURE
YOUR APPLICATION Portmux SDK pb.ingest() pb.transform() pb.sync() pb.webhook() REST API POST /v1/migrate WEBHOOKS on.complete() YOUR CODE App logic Data models Business rules User auth UI / Frontend Database Salesforce Legacy DB CSV / SFTP Other SaaS Another Build
EXAMPLE, 4 LINES TO MIGRATE SALESFORCE
// In your app's data initialization
import { Portmux } from '@portmux/sdk';

const pb = new Portmux({ project: 'your-project-id' });
const patch = await pb.ingest('salesforce', {
  objects: ['Contact', 'Opportunity', 'Account'],
  transform: yourSchemaMap,
  destination: db.collection('customers')
});

// That's it. Portmux handles auth, pagination,
// rate limits, retries, and reconciliation.
01

Replacing SaaS with your own build

You built a better CRM / support tool / ERP. Now you need 5 years of customer data out of the old system and into yours, every field, relationship, and attachment intact.

02

Multi-source ingestion into a platform

Your product aggregates data from your customers' systems. Portmux becomes your integration layer, pre-built connectors, normalized schemas, an SDK your devs own.

03

Post-acquisition consolidation

PE portfolio bought three firms on three different stacks. Consolidate every tenant into the winning system, SaaS or custom-built.

04

Legacy modernization without rewriting

A mainframe, a Lotus Notes install, a FoxPro database. Portmux extracts, transforms, and routes into your modern stack, no COBOL expertise required.

§ 03, PROCESS

Three tracks.
One clean switch.

Every Portmux engagement runs the same discipline whether you're migrating into Snowflake or into a codebase your team deployed last Tuesday.
01
CONNECT

Plug in the source.

A read-only connector indexes the source, SaaS or custom, generates a schema map, and flags every custom field, attachment, and relationship.

→ 24–72 hrs
→ Zero writes to source
→ APIs, DBs, files, or webhooks
02
MAP

Map the schema.

Our engineers draft a field-level mapping document, including custom adapters for proprietary schemas. You approve it before a single record is written.

→ Custom transform functions
→ Deduplication rules
→ SDK integration test suite
03
CUTOVER

Flip the connection.

Dual-write staging keeps both systems in sync during rehearsal. On cutover day, we flip traffic to the destination. Your team keeps building.

→ Rehearsal dry-runs
→ Reconciliation report
→ 30-day rollback window
§ 04, COVERAGE

150+ SaaS connectors.
Plus yours.

Off-the-shelf connectors for the major platforms. Custom adapters for everything else. If your system has an API, a DB, or an export, we migrate it.
Don't see yours? That's the point, we build the connector →
§ 04.6, FIELD NOTES

What we've learned
in the wires.

Long-form writing on data migration risk, cost, planning, and the engineering decisions that make or break a cutover.
§ 05, TRUST

Built for
regulated industries.

Portmux handles PHI, PII, financial records, and export-controlled data every day. Our controls go beyond checkbox compliance.

● ENCRYPTION

End-to-end, in flight and at rest.

AES-256 at rest. TLS 1.3 + mTLS in transit. Customer-managed keys on request.

● RESIDENCY

Your data never leaves your region.

US, EU, UK, APAC deployment zones. HIPAA BAAs, GDPR DPAs on file.

● ACCESS

Zero-standing privilege.

Time-boxed, ticket-bound access with full session recording.

● AUDIT

Every record, accounted for.

Row-level reconciliation report delivered at go-live and archived for 7 years.

SOC 2 TYPE II HIPAA GDPR ISO 27001 PCI DSS
§ 07, QUESTIONS

Before you migrate.

How long does a data migration take? +

Single-system migrations (Track A) typically run 4–6 weeks from kickoff to cutover. Multi-system consolidations (Track B) run 8–12 weeks. Enterprise and M&A migrations (Track C) run 12+ weeks. The pace is set by your team's availability for mapping review, not by our engineering throughput.

Can you migrate from Salesforce to HubSpot? +

Yes. Salesforce to HubSpot is one of our most common CRM migration paths. We handle contacts, companies, deals, custom objects, attachments, and activity history with full field-level mapping and zero data loss. We also support HubSpot to Salesforce, Pipedrive, Zoho, and Microsoft Dynamics migrations.

What happens on cutover day during a platform migration? +

Nothing dramatic. We use a zero-downtime cutover approach with dual-write staging. Both systems stay in sync during a rehearsal window. At the scheduled time we flip your application traffic, run a final reconciliation pass, and sign off. Your end users don't experience a freeze.

How much does a data migration cost? +

Single-system switches start from $12K. Multi-system consolidations start from $38K. Enterprise and M&A migrations are custom-quoted. Final price depends on object volume, custom field count, and integration complexity. We scope it on a 20-minute call before any commitment, no hourly billing.

What if you don't have a connector for my system? +

We build it. Custom connector development is scoped into your engagement, typically 1–3 weeks of additional lead time. Any system with an API, a database driver, or a structured file export is fair game. We've migrated data from legacy mainframes, FoxPro databases, and flat-file SFTP drops.

Can we run the migration ourselves after setup? +

Yes. Track B and C customers can license the Portmux engine post-engagement for ongoing data sync, divestiture events, or future tenant migrations. Ask about Portmux Rails, our self-serve migration platform for repeat movers.

What's the rollback plan if something goes wrong? +

The source system stays authoritative until you sign off on reconciliation. During the rollback window (30 or 90 days depending on track) we maintain a hot-standby that can be re-promoted in under an hour. Every record is accounted for in a row-level reconciliation report.

§ 08, NEXT CUTOVER

Book a 20-minute
scoping call.

Tell us what's in the source, where it's going, SaaS or custom, and when you need to be live. You'll walk away with a scoped quote, a named engineer, and a go-live date.

By submitting, you agree to our Privacy Policy. We'll only use these details to follow up on your migration inquiry.