CRM

Copper Data Extractor

Vern's Copper extractor imports a new user's full Copper — companies, opportunities, projects, and people — into your product as clean, normalized tables. It's built for teams onboarding customers off Copper: pull their records at signup so they land in your app with their history already in place, no manual export and no API plumbing on your side.

Start migration

Browse all extractors

Copper

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 Copper objects (4 total), including: Companies, Opportunities, People, and Projects.

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 crm system (AgileCRM, Apptivo, Capsule CRM) 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 Copper 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. See Copper's authentication guide.

Pagination

Vern detects and handles Copper'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

Copper enforces its own API rate limits (see Copper's rate-limit docs). 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 Copper
curl -X POST https://app.vern.so/api/v1/migrations \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Copper → Postgres", "source": "Copper" }'
→ { "migration_id": "mig_..." }
2. Generate the extraction recipe (pulls live via the Copper 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 copper_export.csv

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

View docs

Common questions

Can I keep a user's Copper data in sync after the first import? Vern supports re-running an import on demand; incremental change tracking depends on what Copper's API exposes for each object.

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

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