Switching to NetSuite Connector from Existing Integration

Learn to switch to NetSuite Connector smoothly by avoiding duplicates and ensuring data integrity during integration.

·2 min read·View Oracle Docs

Switching to NetSuite Connector from an existing integration requires careful handling to prevent issues such as duplicate or missing items and orders. It is crucial to maintain your previous service while activating the NetSuite Connector to ensure a seamless transition.

If your organization has been using another service for syncing items, orders, or other critical data, continue operating that service while you set up NetSuite Connector. This method will safeguard against data loss during the activation of the new connector. If you are currently performing manual updates—keeping items current or manually entering orders—it's essential to follow the procedures documented in the NetSuite Connector's deployment guide to production.

Preparing for Switch

Before you fully activate NetSuite Connector, it's beneficial to execute tests using sample orders and items. This allows you to verify that everything works correctly. Once you're prepared to make the switch, deactivate your existing services or stop any manual processing prior to activating the sync functionality of NetSuite Connector.

Setting Order Cutoff Date

To execute a smooth transition, you should establish an order cutoff date. Note the timestamp of the last order that was posted by your previous integration. Use this timestamp and set it to one minute later in the Import Orders Created After field located on the NetSuite Connector Order Settings page. This step is vital to ensure that no orders are unintentionally skipped or replicated during the import process.

Important Note: NetSuite Connector only imports open (unshipped) orders. If you need to bring in older, fulfilled orders, you will have to utilize the CSV file import feature instead, as this functionality is not included in the standard setup for NetSuite Connector.

Key Steps for Transition

  • Continue existing integrations: Maintain any existing service while activating NetSuite Connector.
  • Set a cutoff date: Determine the last order posted and set the import parameter accordingly.
  • Focus on open orders: Remember that only unshipped orders will be imported; fulfilled orders require a different process using CSV.

This careful approach to transitioning to NetSuite Connector will facilitate smoother operations and maintain data integrity, crucial for business continuity and performance.

Frequently Asked Questions (4)

Do I need to keep my previous integration active while setting up NetSuite Connector?
Yes, it is recommended to maintain your previous integration active while setting up NetSuite Connector to prevent data loss and ensure a smooth transition.
How can I ensure orders are not duplicated during the transition to NetSuite Connector?
Set an order cutoff date by noting the timestamp of the last order posted by your previous system and input this into the NetSuite Connector to avoid duplicating orders.
What should I do if I need to import older, fulfilled orders into NetSuite Connector?
NetSuite Connector does not import older, fulfilled orders by default. You will need to use the CSV file import feature to bring in such orders.
Is testing necessary before fully activating NetSuite Connector, and if so, how should it be conducted?
Yes, testing with sample orders and items is beneficial before activation to ensure everything works correctly. Conduct these tests in accordance with the NetSuite Connector deployment guide.
Source: Switching to NetSuite Connector from an Existing Integration Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Integration

View all Integration articles →