Migration Services

General

Recharge Migration Services are subject to and governed by the Recharge Terms of Service. Migration Services are reserved for merchants on Pro and Custom Pricing plans who are migrating subscriptions to Recharge. These services are designed to provide an elevated level of engagement throughout the lifecycle of a Recharge migration project. All Migration Services projects include:

• Recharge migration project management
• Priority Migration Engineering support through key migration milestones (as defined by formatting policy)
• Post-migration QA, support, and summary

Third party

DEFAULT POLICY

Test migration recommended

This policy applies when a merchant or their partner agency format and validate all migration data, include:

• Data retrieval from legacy platform
• Recharge migration CSV formatting
• Data validation in the Recharge migration tool

Recharge owns import after validation

Conditions:

• Pre-import data issues / data fixes will be owned by the external team
• Data validation troubleshooting supported by Recharge
• Recharge will advise and support but does not own issues or re-work related to the data provided
• Recharge does not audit formatting scripts or advise directly on custom coding against legacy data structures
• Files will be uploaded and fully validated in the Recharge migration tool prior to import. If the file is not ready or there are pre-import validation errors on migration day, the migration may be subject to rescheduling.

If an external team begins formatting under this policy and then changes to a new policy, the formatting effort will start over and the project timeline will be adjusted based on the new policy.

Scheduling Policy (Third Party):

• 2 week minimum, date based on availability

Automated

Requirements:

• Migration scope and data requirement confirmation
• Fromplatform API credentials

Automated

Test migration recommended

Merchant approval of formatted data is required before all test and final imports.

This service covers projects migrating from supported platforms in the Recharge Migr8 feature. This is a commonly used service that also covers basic product mapping as needed.

Scheduling Policy (Automated):

• 2-3 week minimum, date based on availability

Automated Plus

Test migration required

Merchant approval of formatted data is required before all test and final imports. Test migrations are required for any project involving custom formatting by the Recharge team.

This is a service that involves manual intervention for migrations from supported platforms in the Recharge Migr8 feature This is a also commonly used service that covers additional things like:

• Bundle mapping
• Merging customer, subscription, and payment method files
• Data cleaning (duplicate removal, pricing updates, product swaps, discount codes, etc)

Scheduling Policy (Automated Plus):

• 3-4 week minimum, date based on availability

Custom

Standard Custom

Test migration required

Merchant approval of formatted data is required before all test and final imports. Test migrations are required for any project involving custom formatting by the Recharge team.

This policy covers consolidation of data from 1-3 files into a single Recharge migration CSV template, including:

• Payment method mapping
• Product mapping
• Merging customer, subscription, and payment method files

Requirements:

• Migration from a productized subscription platform (not full custom)
• Migration scope and data requirement confirmation at migration kickoff
• Confirmation of access torequired data
• Data sample at migration kickoff

Scheduling (Standard Custom):

• 4 week minimum, date based on availability

Timeline requirements:

Files must be provided in their final format a minimum of 2 weeks prior to test migration. If data structure changes between test migration and final migration, the project will be subject to scope change review and rescheduling.

Advanced Custom

Test migration required

Merchant approval of formatted data is required before all test and final imports. Test migrations are required for any project involving custom formatting by the Recharge team.

This policy covers advanced technical formatting, involving more extensive involvement from the Migration Services and Engineering resources, including:

• Data consolidation from > 3 files
• Date calculation
• Custom pricing logic
• Custom subscription for cart property creation

Requirements:

• Migration scope and data requirement confirmation at migration kickoff
• Confirmation of access torequired data
• Data sample at migration kickoff

Scheduling (Advanced Custom):

• 6-8 week minimum, date based on scope and availability

Timeline requirements:

Files must be provided in their final format a minimum of 2 weeks prior to test migration. If data structure changes between test migration and final migration, the project will be subject to scope change review and rescheduling.