Skip to content


Tech Tuesday: SmartConnect 21 Import Process

The import process for SmartConnect 21 is a bit different than it was in SmartConnect 2018. This article will show how the import process works in SmartConnect 21.

NOTE: You can NOT import exports of SmartConnect 2018 integrations into SmartConnect 21. Only exports from SmartConnect 21 can be imported.

The first step to importing in SC 21 is to enter a SmartConnect temporary file location. This can be found under File > Maintenance > Setup. If you try to import before you have this temporary file path entered, then you will receive the below message.

Once a temporary file location has been entered, then you are able to import integrations. Navigate to the integrations tab and select Import.

This will bring you to the file selection window. Click the file icon on the right to select your exported integrations. You can select as many integrations as you would like to import. Once they have been selected, click “Next”.

The next window allows you to select and deselect any integrations before importing. You can uncheck or check any integration that you may not want to import. All your integrations will be checked by default.

Select “Next”.

The Setup Integrations window is where you configure each import. There will be a red “x” next to any integration that still needs to be configured. If you hover your cursor over the red “x”, then you will get a detailed messaged about why it can’t import yet. Double click each import to open the setup window.

The setup window is where you setup the Data Source, Destination, and any additional setups.

NOTE: Connections will need to be created before importing any integrations that plan on using that connector. You will need to select the connection during the import process.

  • Data Source – This is where you enter info on where you want your source stored (if it is a file source) or what connector you would like to use for the source. You can check the “Use Existing Data Source” checkbox if you already have the data source created in SmartConnect. Otherwise for file data sources, you will need to select the file path to where you want the file to be located. If the data source is not a file data source, then you will need to select the connector being used for the new value.
  • Destination – This is where you need to enter the new values for the destination. Select the connector instance that is setup in SmartConnect and then select the correct entity that the integration is using. If the destination is a file destination, then you will need to enter the file path for the new value.
  • Additional Setups – This is where you enter any additional info that the integrations may have from any additional fields. Some of these values may populate themselves after selecting a destination and other times you may need to select the new value manually. If you had a SQL lookup additional column, then you would need to select the SQL connector that you would want to use.

Hit “Save” when all your new values have been entered.

The red “x” should be gone when the integration is ready to be imported. If the red “x” is still there, then make sure to hover over the “x” with the cursor to see the error message as to why it cannot be imported yet. Click the “Next” button to start the import.

Once the import has completed, you will receive a message saying it was successful or it failed. If the import failed, then hit the “Next” button and that window will explain why the import failed.

You should now be able to open the integration in SmartConnect and start using it.

If you have any questions, feel free to reach out to us at


  1. Francisco N G Hillyer on June 10, 2021 at 10:03 pm

    Would you then be having updated sample integrations for version 21?
    I see in the blogs and eOneSolutions website sample downloadable integrations, but as mentioned, they cannot be imported, so are there any plans to make the blog posts V21 compatible?

  2. Luis de Rivas on March 21, 2023 at 1:47 am

    How do we export variables/maps/data sources/connections fro one server instance to another?? This used to be easy and straight forward in prior editions. Now I have no idea how to move data sources/connections between servers, nor how they relate to tenancy. The manual isn’t much help.

  3. Patrick Roth on March 23, 2023 at 1:09 pm

    You never could “move connections between servers” even on SC 2018 and prior.

    In order to import a map from one system to another you export it on the one system and import it on the second system;

    Now that one that _appears_ a bit different is that we can’t export just data sources. We only export the map. However if you use a translation table and multiple data sources and/or whatever, those all export with the map.

    Then when you import it on the other SC 21 system, since we now allow multiple connectors you have to tell SC which connection to use. Again you would have to have had that set up prior.

    While the UI is indeed different between SC 2018 & SC 21, the idea behind the import/export process is pretty similar and the only “extra step” is that we have to choose the specific instance of CRM/SF/BC/GP etc when importing it back in.

  4. Luis de Rivas on April 2, 2023 at 2:21 pm

    I beg to differ, coming from SC2014, I could select maps, connector objects, etc:

    SC21 Export/Import is madness compared to SC2014. ‘Current’ value where? -The SC21 system I’m importing into or the JSON file? ‘Use Existing Data Source’ -again, what’s the reference? Existing on the ‘current’ SC21 system, or the ‘current’ JSON file?

    If I select ‘Use Existing Data Source’ – the ‘current’ value becomes the Data source in the JSON file. If I want the ‘New’ value to be the ‘Current’ value (after all this is an import process) do I simply leave the ‘new’ value blank?

    I find there is no way have the import process use the data source in the JSON file as the ‘Current’ and ‘New’ value. I simply want to import a map with the data source as it was defined on the system it was exported. I’m not going to manually define the data sources on the target SC21 system…this is the point of the export/import process.

    The destination recognized a GP Connection from the JSON file, but the current value is blank?!?

  5. Patrick Roth on April 5, 2023 at 11:43 am


    “I beg to differ, coming from SC2014, I could select maps, connector objects, ”

    Yes, the export process is now different in that you only select maps which then does all the “map, connector object, etc” so that you can’t “forget” to select a translation table or whatever else the map requires like you could in SC 2018.

    “‘Current’ value where?”

    The “current value” is “what/where do you want to import TO”. Since we can now have multiple connetions/instances per connector (where we couldn’t in SC 2018) now you have to pick.

    “I find there is no way have the import process use the data source in the JSON file as the ‘Current’ and ‘New’ value”

    You are correct. Importing a map to SC 21 you do have to define the target (New Value) of each thing you are importing.

    While I see why it is what it is, does seem if you just have ONE connector set up (BC in the example here) we could default that for you at least.

    You can enter a suggestion for this here:

    If you have further questions on this topic, please open a new support case by emailing or else start a forum post for smartconnect as comments to a blog post really isn’t a good way to discuss (or track) this.


Leave a Comment


Tech Tuesday: Popdock - Joining the tale of two States
Meet eOne Solutions at Directions EMEA 2023!
Connect with eOne Solutions at SuiteWorld 2023!
What is a Data Lake/Data Lake Management?
The Challenges & Benefits of Ad Hoc Reporting


2016 SmartConnect Integration Bootcamps
Tech Tues: Automatically refreshing Pivot Tables in Excel Refreshable Reports
Happy Thanksgiving from the eOne team!
2017 SmartConnect Integration Bootcamps
New Releases of Extender and SmartList Builder



Business Central CRM D365 Business Central Dynamics 365 dynamics crm Dynamics GP Dynamics NAV Econnect Employee Spotlight eone eOne News error Error Message Events Excel Excel Report Builder Extender Flexicoder GP integration Map Microsoft dynamics crm Microsoft Dynamics GP Navigation List Builder Office Relationships Partner All Hands Call Popdock promotions release Salesforce SmartConnect SmartConnect Bootcamp SmartConnect Maps SmartConnect Office Hours SmartList SmartList Builder SmartPost SmartView SQL Tech Tuesday Templates training Zendesk

Integrate & Automate without Any Code.

SmartList Data has Never Been Faster.

The Easiest Way to Report on GP Data.