Skip to main content
Migrating to Quivly is not a data dump-and-load. Quivly connects directly to the systems your data already lives in — Salesforce or HubSpot, Stripe, support, calls, Slack, and your warehouse — the same sources your old tool was reading from. So most of your data isn’t migrated at all; you reconnect the source and it flows in live. What you do migrate is the layer that only existed inside the old tool: your health-score model, playbooks, segments, and any data you kept only there.

​
What carries over vs. what you rebuild

Quivly has no bulk CSV importer for core records, and it never writes back to your source systems. Connecting the integration is the import. Data that lives only in your old CS tool is handled in Backfilling tool-only data.

​
The migration playbook

1

Connect your sources

Connect CRM first, then billing, support, calls, Slack, and usage. Each source populates customers and their history automatically. See the quick start.
2

Verify customer matching

Records from different systems link to one customer profile by email domain and external IDs. Confirm they resolved correctly — see cross-system linking.
3

Rebuild your health-score model

Translate your old scorecard into Quivly’s weighted categories — revenue, usage, engagement, support, market signals. See health score configuration. You can test it against real customers before going live.
4

Recreate segments and views

Rebuild your books of business and risk segments as custom views with filters and saved columns.
5

Rebuild playbooks as agents

Each playbook or CTA rule becomes an agent: a trigger (health change, record update, schedule, Slack) plus steps, with a Review gate before anything sends. See the template agents for common patterns.
6

Backfill tool-only data

Move any data that lived only in the old tool — see below.

​
Coming from another CS platform

Your accounts, contacts, renewals, and tickets already live in your CRM, billing, and support tools — connect those and they sync. From the CS platform itself you only need to carry over what was unique to it: the scoring logic, playbooks, and any custom data. Most platforms export the latter via a CSV/report export or their API. The pattern is the same for any tool: don’t re-export what your CRM/billing already owns — re-express the scoring and automation logic, and backfill only the truly tool-specific data.

​
Coming from a CRM or spreadsheets

If today’s “system” is just your CRM (or a spreadsheet feeding one): connect the CRM and you’re most of the way there. Fields that lived only in a spreadsheet — renewal notes, onboarding stage, a manual risk flag — become custom fields on the customer, or a custom object for repeating records like success plans. Get the values in by writing them to your CRM (so they sync) or via the backfill options below.

​
Backfilling tool-only data

For data that isn’t in any connected source, in order of preference:
  1. Write it to a connected system. The cleanest path — add the field/value in your CRM and it syncs into Quivly like everything else, and stays current.
  2. Model it as a custom object or field, then populate it. Good for success plans, onboarding stages, or account-level flags. See custom objects and custom fields.
  3. Push usage history via the Usage Push API if you’re carrying historical product-usage events.
  4. Ask us. For a large one-time backfill, email support@quivly.ai — book time with the team if you’d like a hand planning the move.

​
FAQ

No. They sync from your CRM. Exporting and re-importing them would create duplicates that fight the live sync. Connect the CRM instead.
There’s no CSV importer for core records — Quivly builds its customer model from your connected systems. Data that isn’t in any source is handled through backfilling: write it to your CRM, or model it as a custom object/field.
No — Quivly computes health from your live data using the model you configure, so scores start fresh and build history from your connect date forward. Underlying history (revenue, usage, calls) still syncs, so trends fill in quickly.
Most teams are live in less than a week, mainly gated by initial sync volume and rebuilding the health model and playbooks. See the implementation FAQ.
Yes. Quivly’s data integrations are read-only, so connecting them changes nothing in your source systems — you can run both in parallel until you’re ready to cut over.