Migrations and integrations for POS, e-commerce and accounting
Move data between the systems a business actually runs on.
Catalogs, customers, orders and sales history, moved between point-of-sale, e-commerce and accounting platforms. Two ways in, one set of connections.
Flow Marketplace
Pick a path, connect two accounts, run it.
Every migration and integration is a listing. Choose one, connect source and target, map the fields, and watch the push jobs run.
- Guided setup for every supported system
- Field mapping validated before anything is written
- Push-job dashboards with logs, abort and restart
Unified API
One contract per vertical. Read and write.
Retail POS, Restaurant and Accounting contracts define 15 entity types with one schema each. Read from any connected system in that shape; write in that shape to any system that accepts writes.
- GET and POST /unified/{accountId}/{entityType}
- LinkToAny holds each platform's OAuth and token lifecycle
- TypeScript SDK with retries and cursor pagination
Paths
Listings people run most.
Every path is a listing with its own field mapping and entity set. Partners get a branded marketplace on their own subdomain that shows only their paths.
Systems
What connects today.
Eleven of these are also on the Unified API: Clover, Square, Shopify, the three Lightspeed series, Toast, Shift4, QuickBooks Online, Xero and Cin7 Core.
Point of sale
- Clover
- Square
- Lightspeed X, R, K
- Toast
- TouchBistro
- Revel
- Shift4
- ShopKeep
- Brink
- Greenline
- RainPOS
E-commerce
- Shopify
- WooCommerce
- BigCommerce
- Magento
- Wix
- PrestaShop
- Etsy
- Amazon Seller Central
Accounting & inventory
- QuickBooks Online
- QuickBooks Desktop
- Xero
- Sage
- FreshBooks
- Zoho Books
- Cin7 Core, Cin7 Omni
- Katana
- Unleashed
CRM, marketing, ops
- HubSpot
- Salesforce
- Klaviyo
- Zoho CRM
- Microsoft Dynamics 365
- Stripe
- Chargebee
- Promenade
- SynergySuite
- Flipdish
How a migration runs
Three stages, all visible.
Connect both accounts
OAuth or API token, depending on the platform. The Marketplace walks through each one.
Map and validate
Source fields line up against the target schema. Nothing is written until the mapping validates.
Push jobs run
Each entity becomes a push job with its own status and log. Abort or restart from the dashboard.
For developers
The API, plainly.
Send an API key as a bearer token. Calls count against a per-organisation budget, 60 requests a minute by default, and LinkToAny paces requests to each platform's own limit underneath.
- SDK
- @linktoany/sdk for Node.js 18+, CJS and ESM, no runtime dependencies
- Auth
- ak_ API key sent as a bearer token
- Hosts
- api.linktoany.com, api.staging.linktoany.com
- Agents
- llms.txt and llms-full.txt on the docs host
// List customers from a connected account
import { LinkToAny } from '@linktoany/sdk';
const client = new LinkToAny({ apiKey: process.env.LINKTOANY_API_KEY });
const page = await client.records.list(accountId, 'customer', { pageSize: 50 });Open the Marketplace, or write to us.
Questions about a path that is not listed yet go to support@linktoany.com.