Skip to main content
This checklist is the working document for a migration to Alguna: the business and pricing information we need from you, the data we import, the integrations we connect, the tests we run before cutover, and the checks on either side of go-live. Alguna’s team runs the migration with you — auditing the current setup, mapping pricing, importing data and monitoring the first cycle — so use this page to prepare and to track progress. The overall sequence is on Migrations; the objects being populated are described in How Alguna works.

​
How Migration Works

​
Pre-Migration Checklist

​
Business Information

  • Legal entity name
  • Business address
  • Tax registration numbers (VAT, GST, etc.)
  • Default currency
  • Invoice branding (logo, colors)
  • Current pricing tiers and plans
  • Usage-based components (metrics, units, rates)
  • Discounting policies
  • Contract terms (commitment periods, renewal terms)
  • Custom pricing for enterprise customers
  • Billing frequency (monthly, annual, custom)
  • Invoice due dates and payment terms
  • Dunning process for failed payments
  • Credit and refund policies
  • Proration rules

​
Existing Systems

  • Platform name (Stripe Billing, Chargebee, Recurly, Zuora, custom)
  • Number of active customers
  • Number of active subscriptions
  • Monthly billing volume
  • Admin access for audit
  • Payment processor you use today, and whether it is one Alguna connects to
  • Stored payment methods to migrate
  • PCI compliance requirements
  • Multi-currency support needs
  • CRM (Salesforce, HubSpot)
  • Accounting (QuickBooks, Xero, NetSuite)
  • Data warehouse (BigQuery, ClickHouse)
  • ERP systems
  • Tax provider (Stripe Tax, Anrok, or Alguna Tax)

​
Alguna Audit Process

When you engage Alguna for migration, our team performs a comprehensive audit:

​
Step 1: Data Collection

We request exports or API access to gather:

​
Step 2: Pricing Analysis

We analyze your pricing structure and map it to Alguna:
  • Flat fees → Products with fixed pricing
  • Per-seat → Products with quantity-based pricing
  • Usage-based → Billable metrics with aggregation rules
  • Tiered pricing → Volume or graduated tier configurations
  • Custom contracts → Enterprise plans with overrides

​
Step 3: Gap Identification

We identify edge cases and special handling:
  • Grandfathered pricing for legacy customers
  • Mid-cycle subscription changes
  • Pending credits or account balances
  • Partial billing periods during cutover
  • Custom invoice formatting requirements

​
Step 4: Migration Plan Delivery

You receive a detailed migration plan including:
  • Product and plan configuration in Alguna
  • Data import mapping and validation rules
  • Integration setup steps
  • Parallel testing approach
  • Cutover timeline and rollback plan

​
Data Migration Checklist

​
Customer Data

​
Subscription Data

​
Historical Data

For large books the import is scripted against the API — see Doing it programmatically.

​
Integration Setup Checklist

​
CRM Integration

1

Connect CRM

Go to Settings → Connections → Integrations and connect your CRM (Salesforce, HubSpot).
2

Map Fields

Configure field mappings between Alguna accounts and CRM records.
3

Set Sync Direction

Per object type, choose source, target or bidirectional and a conflict strategy — see External sync.
4

Test Sync

Create a test account and verify data flows correctly.

​
Accounting Integration

1

Connect Accounting System

Go to Settings → Connections → Integrations and connect QuickBooks, Xero, or NetSuite.
2

Map Chart of Accounts

Link Alguna revenue categories to your GL accounts.
3

Configure Sync Timing

Set when invoices sync (on issue, on payment, both).
4

Reconcile Test Invoices

Issue test invoices and verify they appear correctly in your accounting system.

​
Testing Checklist

Before going live, verify:

​
Invoice Validation

  • Invoice totals match expected amounts
  • Line items are correctly itemized
  • Tax calculations are accurate
  • Discounts apply correctly
  • Proration calculations are correct

​
Workflow Validation

  • New customer signup works end-to-end (checkout or API)
  • Subscription changes (upgrade/downgrade) work — Updating a subscription
  • Usage events are received and metered — check the failed list on POST /events
  • Payment collection succeeds
  • Webhooks fire for key events and signatures verify

​
Integration Validation

  • CRM records update correctly
  • Accounting entries post correctly
  • Customer portal shows accurate data
  • Emails send with correct content

​
Cutover Checklist

​
Pre-Cutover (T-1 Day)

  • Final data sync from old system
  • Verify all active subscriptions imported
  • Confirm payment methods migrated
  • Test webhook endpoints are ready
  • Notify internal teams of cutover timing

​
Cutover Day

  • Disable billing in old system
  • Run final subscription sync
  • Enable billing in Alguna
  • Monitor first batch of invoices
  • Verify payments process correctly

​
Post-Cutover (T+1 Day)

  • Review overnight invoices and payments
  • Check for any failed payments
  • Verify webhook delivery
  • Confirm accounting sync
  • Document any issues for follow-up

​
Support During Migration

Alguna provides dedicated support throughout migration:

​
Next Steps

Sync Accounts

Import customers from your existing system.

Developer quick start

API keys, sandbox and the endpoints an import script uses.

Integrations

Every connector, by category.

Contact Support

Get help with your migration.