Other

Track PMS Data Extractor

Vern's Track PMS extractor imports a new user's other data — contacts, users, companies, and charges — into your product through a single managed migration, handling Track PMS's auth, pagination, and rate limits for you. It's built for teams onboarding customers off Track PMS who want their data in your app from day one.

Start migration

Browse all extractors

Track PMS

SaaS API (REST)

Managed auth, retries, and throttling

Normalized JSON, CSV, and DB-ready output

Cleaned JSON, CSV, and DB-ready output

Export coverage

Know exactly what Vern pulls before you migrate.

Objects Vern extracts

Vern extracts the full set of queryable Track PMS objects (77 total), including: Accounting Accounts, Accounting Bills, Accounting Charges, Accounting Deposits, Accounting Deposits Payments, Accounting Items, Accounting Transactions, Booking Fees, Charges, Companies, Contacts, Contacts Companies, Contacts Pii Redacted, Contracts, Crm Company Attachment, Crm Tasks, Custom Fields, Date Groups, Documents, Folios, Folios Logs, Folios Rules, Folios Transactions, Fractionals, Fractionals Inventory, Fractionals Owners, Groups, Groups Blocks, Groups Breakdown, Groups Tags, Housekeeping Clean Types, Housekeeping Task List, Housekeeping Work Orders, Lodging Types, Maintenance Problems, Maintenance Work Orders, Nodes, Nodes Types, Owners, Owners Contracts, Owners Pii Redacted, Owners Statements, Owners Statements Transactions, Owners Units, Promo Codes, Quotes, Rate Types, Reservations, Reservations Cancellation Policies, Reservations Cancellation Reasons, Reservations Discount Reasons, Reservations Guarantee Policies, Reservations Types, Reservations V2, Reviews, Roles, Suspend Code Reasons, Tags, Tax Districts, Tax Policies, Taxes, Travel Insurance Products, Units, Units Amenities, Units Amenity Groups, Units Bed Types, Units Blocks, Units Channel, Units Daily Pricing Parent, Units Daily Pricing V2, Units Taxes, Units Taxes Parent, Units Types, Units Types Daily Pricing Parent, Units Types Daily Pricing V2, Users, and Users Pii Redacted. 9 of these support incremental change tracking, so syncs pull only what changed.

Output schema

Normalized JSON per object with referential keys preserved, so the relationships between your user's records survive the import. Timestamps are returned in ISO 8601. Delivered as JSON or CSV, or loaded straight into your own application database or pushed to your API — whatever your product expects.

Where it can land

Your own application database (Postgres, MySQL), a direct push to your API or webhook, or JSON/CSV files, plus another other system (Aviationstack, Bluetally, Breezometer) when a user is switching tools.

Source details

Built for the source type shown above, with extractor content refreshed from the collection record.

Managed by Vern

The details you normally have to build yourself.

Authentication

API key / access token. Your user pastes their Track PMS API key once when they sign up; Vern stores it encrypted and attaches it to every request, handling header signing and retries so you never touch the raw credential.

Pagination

Vern detects and handles Track PMS's paging model (cursor, page-number, or offset) internally and returns one consistent, de-duplicated result set — so you import a user's complete data without ever managing page tokens.

Rate limits and gotchas

Track PMS enforces its own API rate limits. Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.

API-key sources rarely surface their true rate ceilings until you hit a 429 mid-import, and many silently cap page size. Vern throttles to stay under the limit and normalizes paging so a partial pull never lands a user in your product with missing data.

API quickstart

1. Create a migration for Track PMS
curl -X POST https://app.vern.so/api/v1/migrations \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Track PMS → Postgres", "source": "Track PMS" }'
→ { "migration_id": "mig_..." }
2. Generate the extraction recipe (pulls live via the Track PMS API)
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "generate", "extract_via_api": true }'
3. Run the approved extraction
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "execute" }'
4. Download the normalized CSV export
curl https://app.vern.so/api/v1/migrations/$MIGRATION_ID/exports/{template} \
  -H "x-api-key: $VERN_API_KEY" -o track-pms_export.csv

A cleaner way to extract without rebuilding source-specific plumbing.

View docs

Common questions

Can I keep a user's Track PMS data in sync after the first import? Yes — 9 Track PMS objects support incremental change tracking, so after the first full import Vern pulls only what changed on re-run.

Can I move a user from Track PMS to Aviationstack? Yes — Vern normalizes the Track PMS data model into typed tables that map cleanly onto Aviationstack and into your own product.

What does it cost to read the Track PMS API? Track PMS's own API access follows Track PMS's pricing/plan; Vern is billed separately per import. Check Track PMS's developer docs for their current limits.