Migrate To Railz

Welcome to the Railz 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 managed migration process allows you to effortlessly transfer your existing customer connections to Railz, 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 Railz?

  • More Data Coverage: Expand the horizons of your data collection with comprehensive coverage across various platforms and services.
  • Analytics Insights: Gain invaluable insights into your business data through Railz's robust analytics features.
  • Enhanced Normalization: Benefit from standardized data formats, making it easier for you to integrate and analyze the information.
  • Managed Migrations: Our team takes care of the migration process from start to finish, letting you focus on what truly matters—your business.

Migration Checklist

Before diving into the migration process, ensure you have the following:

  • The business names and the accounting service providers (ASP) they are connected to.
  • Access Tokens from all of the ASPs.
  • Refresh Tokens from all of the ASPs.
  • Expiry Date for each Refresh Token.
  • Expiry Date for each Access Token.
  • Provide the Account ID, Business ID, Realm ID or Tenant ID of the ASPs.
  • Subsidiary ID (if applicable).
  • Coordinate a time when the migration can take place. Railz will run the migration on your behalf once all the information has been provided.

Managed Migration Process

(Note: Self-managed migrations are coming soon)

Railz offers a managed migration process to make your transition as seamless as possible. To begin, you'll need to provide us with specific information, which we'll use to facilitate the migration on your behalf. Follow the steps below to get started.

Pre-Migration Steps

  • For Competitor Users:
    • Contact Your Existing Provider: Request access to your authorization keys securely.
    • Provide Key Information: Submit the acquired keys to Railz through a secure channel provided by our team (see table below for details).
  • Data Preparation: Compile all necessary data and token information, as per your existing service provider (see table below).

Required Information by Service Provider

Service ProviderRequired Information for Migration
QuickbooksAccess Token, Refresh Token, Access Token Expiry Date, Refresh Token Expiry Date, Realm ID
XeroAccess Token, Refresh Token, Access Token Expiry Date, Refresh Token Expiry Date, Tenant ID
FreshbooksAccess Token, Refresh Token, Access Token Expiry Date, Refresh Token Expiry Date, Account ID
WaveAccess Token, Refresh Token, Access Token Expiry Date, Refresh Token Expiry Date, Business ID
Sage Business CloudAccess Token, Refresh Token, Access Token Expiry Date, Refresh Token Expiry Date, Business ID
Sage IntacctWeb Service User ID, Web Service User Password, Company ID, Subsidiary ID
Oracle NetsuiteClient Id, Client Secret, Token ID, Token Secret, Account ID, Web Services URL
Dynamics 365 Business CentralAccess Token, Refresh Token, Access Token Expiry Date, Refresh Token Expiry Date, Company ID
QBDUserName, Password, File Id, Owner Id
PlaidAccess Token, Refresh Token, Access Token Expiry Date, Refresh Token Expiry Date, Item Id
SquareAccess Token, Refresh Token, Access Token Expiry Date, Refresh Token Expiry Date, Location ID
ShopifyAccess Token, Refresh Token, Access Token Expiry Date, Refresh Token Expiry Date, Shop ID(.myshopify.com)

Migration Steps

StepStep DescriptionWho is Responsible
Contact RailzContact Railz to express your intent to migrate.Customer
Secure FormRailz Support Team sends a secure form with details of what you need to provide.Railz Team
Form SubmissionUpload the required data.Customer
Data ReviewRailz team reviews the uploaded data.Railz Team
Disable SyncingDisable data syncing in existing applications.Customer
Migration SchedulingCoordinate a time for migration.Customer and Railz Team
Migration ExecutionRailz runs the migration, we will carry out the migration in bits by validating the first token supplied was synced successfully before proceeding to migrating the next set of keys.Railz Team
Initiate SyncTrigger data synchronization.Railz Team
Data ValidationVerify that all the migrated data has been correctly transferred.Customer


Client ID and Client Secret

Ensure you use the same Client ID and Secret that you used when obtaining the tokens for each business. Add these via the Railz dashboard.

Potential Issues and Troubleshooting

Migration processes are often complex and can sometimes run into issues. Below are some potential problems that you could encounter during your migration to Railz, along with suggestions for resolving them.

IssueDescriptionSuggested Resolution
Invalid TokensAccess or Refresh Tokens provided are not validDouble-check the tokens for any typos
Expired TokensThe Access or Refresh Tokens have expiredRequest new tokens from the service provider
Missing DataSome necessary data is missing in the form submissionDouble-check the form for completeness
Incorrect Tenant/Realm IDThe Tenant ID or Realm ID provided does not match with the service providerVerify the ID submitted with the business or reauthorize using Railz
Post-Migration Data Sync IssuesData does not seem to be syncing correctly after the migrationContact Railz support team for troubleshooting
Application ErrorsReceiving unexpected errors in the application after the migrationReport errors to Railz support for resolution
Data Not RetrievedData not retrieved for certain data typesThis 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 managed migration process isn't suitable for your needs, or if you'd prefer to take a different approach, another alternative is to implement Railz's connection flow into your application. This would involve setting up the Railz connection process in your application and inviting your businesses to reconnect their service providers through this new flow.


  • 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 Railz Connection Flow: Follow the documented steps here.
  • User Notification: Notify your businesses about the new update and guide them to reconnect their accounts via the new flow.

Frequently Asked Questions (FAQ)

  • Is self-managed migration possible?
    • Currently, Railz only offers managed migrations. Self-managed migrations are coming soon.
  • How long will the migration process take?
    • The migration duration varies. It's best to 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
Help centre