Integrations & migration
Don't replace your ERP. Make it more useful.
Scale Passport is the operating layer for the scale business. Your accounting or ERP platform remains authoritative for financial transactions and statements.
Keep the financial system authoritative.
Invoice issuance, payments, receivables, taxes, general ledger, and financial statements remain in the accounting or ERP system you select.
Connect the operating record.
Prospects, customers, facilities, contacts, individual scales, evidence, opportunities, quotes, jobs, service records, billing-package approval, and next actions stay organized in Scale Passport.
Integration matrix
Keep what works. Make the handoff clear.
Microsoft Dynamics GP / Great Plains
- Keep it for
- Accounting, financial transactions, GL, AR/AP, and established finance processes.
- Scale Passport role
- Customer, asset, and service workflow with controlled financial handoff.
- Current boundary
- Scale Passport supports a deployment-specific Dynamics GP integration through its ERP adapter architecture. Configuration and validation are required for each deployment.
QuickBooks
- Keep it for
- Accounting and financial system of record.
- Scale Passport role
- Creates and approves billing-ready work before accounting handoff.
- Current boundary
- The accounting-system boundary remains explicit.
Modern ERP systems
- Keep it for
- Corporate financial, inventory, or enterprise functions selected by the company.
- Scale Passport role
- Provides an ERP-neutral operating and adapter layer.
- Current boundary
- Connector scope is deployment-specific.
Excel and CSV
- Keep it for
- Useful historical and analytical files.
- Scale Passport role
- Imports reviewed structured records and keeps recurring operating work in the connected record.
- Current boundary
- Source and provenance stay visible during review.
Google Drive / Docs
- Keep it for
- Existing files and documents.
- Scale Passport role
- Associates document context with the customer, facility, scale, job, and report where the deployment connects those systems.
- Current boundary
- Document connector configuration and access rules require validation.
Calendar, fleet, and legacy systems
- Keep it for
- Existing schedules, vehicle context, and acquired-company applications.
- Scale Passport role
- Supports adapter boundaries for connected jobs, assignments, and validated historical mapping.
- Current boundary
- No named connector is represented as live without deployment-specific validation.
Migration without chaos
Start from the record you have—not the clean starting point you wish you had.
A dealer can begin with accounting exports, spreadsheet customer lists, CSV files, old certificates, PDFs, Google folders, technician files, legacy service software, and acquired-company records. The migration process preserves source and provenance instead of pretending every imported field carries the same confidence.
Spreadsheet customer listsAccounting exportsCSV dataOld certificates and PDFsGoogle foldersTechnician filesLegacy service softwareAcquired-company records
API and portability
Keep the data path open and scoped to the dealer.
Scale Passport uses an adapter model for deployment-specific integrations and supports structured JSON and CSV data exchange. A deployment determines which endpoints, connectors, credentials, and access boundaries are activated; the public site does not represent every interface as a hosted, public production API.
Map your existing systems