Migration Guide

Switching to Quiltt gives you access to multiple data providers through a single integration, enriched financial data, and powerful payment operations. Whether or not you're currently using an aggregator like Plaid, MX, or Finicity, Quiltt provides a smooth migration path.

You can migrate in two ways: import all existing connections at once for a complete switchover, or gradually roll out Quiltt alongside your existing provider using feature detection.

Link to this section#Choosing the Right Approach

Factor	Full Import	Gradual Migration
User Impact	All users switch at once	Phased rollout by institution
Risk	Higher initial risk	Lower, easier rollback
Best For	Small user bases, greenfield projects	Large user bases, A/B testing

Link to this section#Prerequisites

Before migrating, ensure:

1. Provider integration enabled - Configure your provider (e.g., Plaid) in Quiltt Dashboard with your credentials in Test environment first
2. SDK installed - React, React Native, etc.
3. Authentication configured - Issue session tokens from your backend and wrap your app with QuilttProvider

Link to this section#Option 1: Import Existing Connections

For a complete switchover, import your existing provider connections to Quiltt and swap your connector implementation.

Link to this section#When to Use This Approach

• Migrating your entire user base at once
• Replacing an existing provider integration completely
• Need to maintain existing connection history
• Want a clean cutover with minimal code changes

Link to this section#Benefits

• One-time migration process
• Full feature access to Quiltt's enrichment and payment operations
• Centralized connection management
• Simplified codebase with single integration

Link to this section#How It Works

1. Import Connections via API: Use Quiltt's REST API to import existing provider connections (e.g., Plaid access tokens)
2. Swap Connector: Replace your existing connector UI with Quiltt Connector
3. Continue Operations: All existing connections work seamlessly in Quiltt

Link to this section#Implementation Steps

1. Import Connections

Use the Platform REST API to import existing Plaid Items:

Parameters:

• accessToken (required): The Plaid access token or processor token
• externallyManaged (optional): Set to true if you don't want Quiltt to delete the connection from the provider on disconnection
• migrateWebhook (optional): Set to true to update the webhook URL to Quiltt's webhook endpoint

Build a migration script to import all existing connections:

2. Update Your Frontend

Replace your existing connector with Quiltt Connector:

3. Verify Migration

• Test that imported connections appear in Quiltt Dashboard
• Verify data sync is working correctly
• Check that webhooks are being received

Link to this section#Option 2: Gradual Migration with Resolvable Check

For a phased rollout, use the useQuilttResolvable hook to selectively migrate users while maintaining backward compatibility.

Link to this section#When to Use This Approach

• Testing Quiltt with a subset of users
• Running both providers in parallel
• Gradual rollout to minimize risk
• Need to maintain existing provider code during transition
• Migrating institution by institution

Link to this section#Benefits

• Low-risk incremental rollout
• A/B testing capabilities
• Maintain existing provider as fallback
• Easier rollback if issues arise
• Validate institution by institution

Link to this section#How It Works

1. Check Institution Compatibility: Use useQuilttResolvable to check if a provider's institution is supported by Quiltt
2. Conditional Rendering: Show Quiltt Connector for supported institutions, fallback to existing provider for others
3. Gradual Expansion: As you verify success, expand to more institutions

Link to this section#Implementation

Link to this section#Related Resources

• Core Concepts - Understand Profiles, Connections, and Integrations
• Connector Overview - Learn about Quiltt Connector features and configuration
• Authentication Guide - Set up Session tokens for secure API access
• Webhooks - Monitor connection status and data sync events
• Reconnect Flow - Handle connection errors and re-authentication
• Account Aggregation Integrations - Plaid, MX, Finicity, and Akoya documentation
• Platform API Reference - Complete REST API documentation