--- updatedAt: 2026-10-13T13:36:16.000Z --- # Migrate To Accounting Data as a Service™ Welcome to the Accounting Data as a Service™ migration guide. Whether you've partnered with another financial data integration provider or have built your own integrations, you're in the right place. Our self-managed migration process allows you to effortlessly transfer your existing customer connections to Accounting Data as a Service™ without requiring them to go through the reauthorization process. This guide will walk you through the steps to ensure your transition is as smooth as possible. ## Why Migrate to FIS® Accounting Data as a Service™? * **More Data Coverage**: Expand your data collection with comprehensive coverage across various platforms and services. * **Analytics Insights**: Gain invaluable insights into your business data through Accounting Data as a Service's robust analytics features. * **Enhanced Normalization**: Benefit from standardized data formats, making it easier to integrate and analyze information. ## Migration Checklist Before diving into the migration process, ensure you have the following: * Client ID and Secret used when obtaining tokens for each business. * Business names and the accounting service providers (ASPs) they are connected to. * Access Tokens from all ASPs. * Refresh Tokens from all ASPs. * Account ID, Business ID, Realm ID, or Tenant ID of the ASPs. ## Migration Process ### Self-Managed Migration Accounting Data as a Service™ offers a self-managed migration feature that allows you to independently handle the transition of your business connections via our API. #### Pre-Migration Steps * **For Competitor Users**: * **Contact Your Existing Provider**: Securely request access to your authorization keys. * **Provide Key Information**: Submit the acquired keys to Accounting Data as a Service™ through a secure channel. * **Data Preparation**: Compile all necessary data and token information as per your existing service provider (see the table below for details). > 🚧 **Note**: > > Automatic migration cannot be done for these Service Providers: > > * `QuickBooks Desktop` > * `Oracle Netsuite` > * `Sage Intacct` > * `Shopify` > * `Square` > > For these providers, contact us for more details. #### Required Information by Service Provider | Service Provider | Required Information for Migration | | ----------------------------- | ---------------------------------------- | | QuickBooks | Access Token, Refresh Token, Realm ID | | Xero | Access Token, Refresh Token, Tenant ID | | FreshBooks | Access Token, Refresh Token, Account ID | | Wave | Access Token, Refresh Token, Business ID | | Sage Business Cloud | Access Token, Refresh Token, Business ID | | Dynamics 365 Business Central | Access Token, Refresh Token, Company ID | | Plaid | Access Token, Item ID | | ZohoBooks | Access Token, Refresh Token, Account ID | > **Note**: Based on the table above, `accountId` in the API refers to different IDs such as `Realm ID`, `Tenant ID`, `Account ID`, etc., depending on the service provider.
#### How to Perform a Self-Managed Migration 1. **Create or Retrieve a Business**: Begin by either creating a new business with `POST /v2/businesses` or retrieving an existing business using `GET /v2/businesses` to obtain the `businessUuid`. 2. **Initiate Migration**: Use the `POST /v2/businesses/{uuid}/connection/migrate` endpoint to migrate the business connection. Replace `{uuid}` with the `businessUuid` obtained in the previous step. **Request Example**: ```http POST /v2/businesses/{uuid}/connection/migrate ``` **Body Parameters**: ```json { "serviceName": "quickbooks", "accessToken": "string", "refreshToken": "string", "accountId": "string" } ``` Replace `"serviceName"`, `"accessToken"`, `"refreshToken"`, and `"accountId"` with the respective details for the connection you are migrating. Ensure that the refresh token has not expired before initiating the migration. API Reference can be found [here](https://docs.railz.ai/reference/migrateconnection). 3. **Trigger Data Synchronization**: See [Queue Data Sync](https://docs.railz.ai/reference/datasync) for more details. 4. **Verify Data Transfer**: Make API requests to the respective data endpoints to ensure all data has been correctly transferred. ### Potential Issues and Troubleshooting Below are some potential problems that you could encounter during your migration to Accounting Data as a Service™, along with suggestions for resolving them. | Issue | Description | Suggested Resolution | | ------------------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | Invalid Tokens | Access or Refresh Tokens provided are not valid | Double-check the tokens for any typos | | Expired Tokens | The Access or Refresh Tokens have expired | Request new tokens from the service provider | | Missing Data | Some necessary data is missing in the form submission | Double-check the form for completeness | | Incorrect Tenant/Realm ID | The Tenant ID or Realm ID provided does not match with the service provider | Verify the ID submitted with the business or reauthorize using Accounting Data as a Service™ | | Post-Migration Data Sync Issues | Data does not seem to be syncing correctly after the migration | Contact Accounting Data as a Service™ support team for troubleshooting | | Application Errors | Receiving unexpected errors in the application after the migration | Report errors to FIS® Accounting Data as a Service™ support for resolution | | Data Not Retrieved | Data not retrieved for certain data types | This could be due to missing scopes. Check each service provider's documentation for required scopes and possibly reauthorize | If you run into an issue not covered here, please reach out to our support team for personalized assistance. ## Other Migration Alternatives If the self-managed migration process isn't suitable for your needs, another alternative is to implement Accounting Data as a Service's connection flow into your application. This involves setting up the Accounting Data as a Service™ connection process and inviting your businesses to reconnect their service providers through this new flow. ### Advantages * **Complete Control**: You have complete control over the user experience. * **Immediate Authorization**: Businesses can connect immediately without waiting for a scheduled migration. * **Refreshed Data**: By having businesses go through the authorization flow again, you ensure that all data permissions and scopes are up-to-date. ### Steps to Implement * **Implement Accounting Data as a Service™ Connection Flow**: Follow the documented steps [here](https://docs.railz.ai/docs/connection-flow-overview). * **User Notification**: Notify your businesses about the update and guide them to reconnect their accounts via the new flow. ## Frequently Asked Questions (FAQ) * **How long will the migration process take?** * For Self-Managed Migrations, you can check the status of the data synchronization process. For Managed Migrations, the duration varies. Consult with our team for an accurate timeframe. ## Get Support For any migration-related queries or issues, contact our support team. ## Helpful Links [API docs](https://docs.railz.ai/docs)\ [Help centre](https://help.railz.ai/en/collections/3500808-setting-up-your-service-integrations)