Migrate from SuiteSync to the Stripe Connector for NetSuite

Before you begin the connector installation, consider the following:

• Our team provides configuration instructions that reveal the live mode SuiteSync configuration of a specific Stripe account, and assume you’ll continue to use this account with the connector in live mode. We don’t address test mode configurations of SuiteSync.
• If you have more than one Stripe account that uses SuiteSync, you must log into each account separately and receive specific instructions from our team to address a potentially unique configuration. Make sure you follow the account-specific instructions when performing the migration.

Choose the test environment

Decide which Stripe testing environment you want to install the connector in: test mode or sandbox. Note the differences in the table below.

Disable any pre-existing test integrations

Stripe test mode was likely connected to one of your NetSuite sandboxes during the original SuiteSync implementation, or during subsequent testing sessions. It’s possibly still connected now.

SuiteSync and the NetSuite connector can’t reliably operate simultaneously in the same mode for the same Stripe account ID. This applies to Stripe test mode and live mode, but not Stripe sandboxes, because only the connector supports it (and not SuiteSync).

Before you can enable the connector in a Stripe test mode account, you must log into the SuiteSync dashboard to confirm you have no pre-existing test integrations enabled for the Stripe account.

1. Go to the SuiteSync dashboard.

2. Select the sandbox or test account > (your name) > Connection Settings.

   • If you see, “Invalid NetSuite Credentials” or “Real-time Integration Disabled,” this means the test integration is disconnected.
   • If you see, “The NetSuite connection is active. Stripe data is being pushed to NetSuite.” click Disable Real-time Integration.

3. After you disable SuiteSync in test mode, you can follow the instructions below to enable the Stripe Connector for NetSuite on the same test mode Stripe account.

   Alternatively, you can use the current SuiteSync test mode integration if you’re actively testing. Go to the live mode Stripe account and create a new Stripe sandbox instead, and connect to the same or a different NetSuite sandbox. Make sure you create the Stripe sandbox as a “copy” of the live mode account, not a standalone sandbox account. The SuiteSync test instance is now outdated.

Configured components

Both SuiteSync and the Connector App have general settings and workflow-specific settings. They use native, prebuilt Connector App settings or bundle functionality. You generally want to migrate them first.

Stripe doesn’t have full visibility into four types of components for any integration. Our team will review these with you:

• Some native SuiteSync subfeatures that require in-depth analysis to detect usage per account.
• Native bundles that you installed in NetSuite.
• Script templates from SuiteSync that you installed in NetSuite.
• Custom scripts or features built on top of SuiteSync functionality. This includes components built by a Stripe implementation partner, another third-party company, or your team.

These might apply to your specific integration. You can inspect the NetSuite production environment and the Stripe live mode environment in all cases to be certain. You’re responsible for maintaining script templates and custom scripts or features, or engaging a partner to maintain them.

The connector’s endpoint metadata keys and functionalities are mostly unchanged, but we encourage you to test any components you have before the live cutover to make sure they still function as expected. The new connector bundles include changes to many field IDs for equivalent custom fields.

SuiteSync and NetSuite connector bundles

The Connector App has connector-specific bundles and some bundles that SuiteSync also uses. We updated bundle names and descriptions from “SuiteSync” to “SCN” or “Stripe” before we released the Stripe Connector for NetSuite. This might cause some confusion. Make sure to distinguish the bundle IDs in the instructions our team provides from SuiteSync bundles that have similar names and functionalities. They’re different and SuiteSync-specific bundles won’t work with the Connector App’s updated features.

Before you begin, you must open the Stripe Dashboard in test mode or create a Stripe sandbox account that’s associated with your live mode account.

1. Go to the Stripe Dashboard for your account.
2. While in live mode, click your account name > Switch to sandbox.
3. Select Create sandbox or Test mode.
4. If you selected Create sandbox, click Copy your account.

Install the Connector App

Next, install the Connector App in the test mode or sandbox account that you selected.

1. Go to the Stripe App Marketplace > Stripe Connector for NetSuite page.

2. Do one of the following:

   • For test mode, click Try it in test mode.
   • For a sandbox, click Install app.

3. Confirm the permissions.

4. The app installs automatically on your selected account. Click the letter “S” (S) icon to open the side drawer view of the app.

5. Click View App Settings to continue setup.

6. On the setup page, start the in-app wizard to connect Stripe and NetSuite with token-based authentication.

7. Follow the wizard to complete the setup.

   Caution

   If you have multiple sandboxes, you must select the NetSuite sandbox account to connect to the Stripe test environment. If you previously configured SuiteSync in the NetSuite sandbox, you might have the Stripe Token Based Authentication bundle (previously called SuiteSync Token Based Authentication) with the bundle ID 178262 installed. Both SuiteSync and the Stripe Connector for NetSuite use this bundle. If the bundle or integration name is still SuiteSync, you can select that integration record in NetSuite and the connector still functions properly. In production environments, the tokens for SuiteSync functionality rely on this bundle for continuity through the live cutover.

8. After successfully connecting the Stripe and NetSuite environments, you’ll see the App Settings page to configure the tabs.

Our team will guide you through the migration process. We’ll cover:

• Your unique SuiteSync configuration for each Stripe account.
• The migration process for the workflows you use.
• Information about updated workflows and new functionality.
• How to get started with the migration.

Follow the steps in the personalized migration guide that you receive from our team to configure your Connector App.

Test the connector settings that you configured in test mode or a sandbox, including Stripe record creation and syncing to NetSuite.

Test custom features or scripts

You’re responsible for maintaining script templates and custom scripts or features, or engaging a partner to maintain them. This includes knowing the necessary workflows and testing procedures. Stripe has no visibility into any customizations because they’re typically built upstream or downstream of the connector in the integration flow.

When you’re ready for the live cutover, contact us using the migration support button in the Connector App. Make sure you allow enough time before any internal cutover deadlines.

The Stripe Connector for NetSuite team will schedule a call with you to review the accuracy of your configuration and manage the timing of the live cutover.