If you’re moving from SmartConnect.com or SmartConnect 21 to the new SmartConnect, or you’re a partner helping your customers make the move, this article walks through what’s changed and what stays the same across every part of the app. It also covers the connectors available today and what to expect when you migrate. Use it to plan your move with confidence and to discover the new capabilities now available to you.
- Licensing
- Migrating to the New Platform
- User Interface
- Security
- Data Sources
- Integration Building
- Processing, Monitoring & Troubleshooting
- API & Connectivity
- Connectors
- Upcoming Connectors
Licensing
All SmartConnect subscription customers have dual access to continue to run their existing SmartConnect.com/SmartConnect 21 integrations while they build their new integrations on the new platform.
Existing Customer Access
Currently access to the new version is opt-in only. If you are interested in getting access send an email to sales@eonesolutions.com and include the following information:
- What is your company name?
- What Applications are you planning to integrate?
- Are you interested in receiving assistance on the migration from our Professional Services Team?
Partner NFR Access
Any partners wanting access to the new version for demoing, and internal training purposes can reach out to sales@eonesolutions.com or your account manager and include the following information:
- What applications and scenarios is your team interested in?
- Who at your organization needs access?
New Customer Access
Currently our solution architecture team is evaluating all new customers to determine if they are a fit for the new version of SmartConnect. Once we reach product partity later in the year between the SmartConnect versions, we will automatically onboard all new customers onto the new platform.
Migrating to the New Platform
Moving to the new SmartConnect is a guided process. Today, migrations are handled hands-on by eOne Professional Services, or by your partner, who rebuild your integrations on the new platform with you. A self-service migration tool is planned for a future release. Until it’s available, this guided approach ensures your integrations are moved over carefully and tested before you go live.
Is now the right time to migrate?
- Simple integrations are the best fit today. A handful of integrations on standard connectors with straightforward mappings will migrate quickly and smoothly.
- Make sure your connectors are available. If a system you rely on isn’t on the new platform yet, it’s worth waiting until it is. Check the connector sections above for what’s available now, and reach out to eOne or your partner to confirm timing before you plan your move.
- If your integration needs are already changing, now is a good time. If you’re moving between systems anyway (for example, from Dynamics GP to Dynamics 365 Business Central), your integrations will need to be redesigned regardless, so it makes sense to rebuild them on the new platform.
What can make a migration more involved
Most integrations migrate in a straightforward way. A few things can mean some parts need to be rebuilt or adjusted rather than carried over directly:
- Extensive scripting or custom logic in mappings. Heavy scripting often needs to be reviewed and rebuilt rather than carried over directly.
- A large number of calculated columns or restrictions. These take time to recreate and verify on the new platform.
- A dependency on a connector or feature that isn’t available yet. The integration can’t move until everything it relies on is on the new platform.
- Multiple interdependent integrations. When integrations have to move together, they add coordination and testing effort.
User Interface
The new platform replaces the legacy interface with a modern UI that aims to simplify the integration building process and provide better visibility. The core building blocks of an integration carry over, but where you find things, and how you monitor and edit them, has changed.
What’s the same
- Naming conventions – Have stayed the same giving you a familiar footing
What’s changed
- Modern eOne design language – Aligned with Popdock design
- Linked resource counts – View how many records are in a related menu at a glance
- Enhanced Integration Import Wizard — Modify any detail of an integration when importing it
What’s new
- Process Canvas — Visual interface showing how integrations interconnect
- Current Runs — Real-time visibility into all running processes
- Drafts — Edit an integration without affecting the live version
- In-app contextual help – For the specific area you’re working in
- AI Markdown export — Export integration config as Markdown for AI tools
Security
Security moves from basic permissions to granular, role-based control, backed by a full audit trail. Together these provide the enterprise-level security our customers require.
What’s the same
- Password policy – Define your own password requirements
- Unlimited users – No limit on the number of users you can grant access to
What’s changed
- Granular role-based security – replaces basic permissions, letting you control who can view, edit, or create in SmartConnect
What’s new
- Audit trail – Track who changed what and when, and view deleted objects
- Team-based security – Use teams to assign user permissions in bulk
- User management – Reset user passwords and view login history
Gaps & deprecations
- Integration-level security – Coming in a future update
Data Sources
Source handling is one of the most enhanced areas of the platform on day one. Custom filters and calculations are now available across all sources regardless of whether the underlying connector supports them natively, and realtime sources use a new, more resilient processing model.
What’s the same
- Building a data source – Choosing a source, selecting the fields you need, and mapping them to your target works the way it does today
- The data sources you use today – Your existing source types carry over to the new platform
What’s changed
- Realtime data sources now use a staging table – Resilient webhooks where the webhook is decoupled from the integration run, allowing better performance under load
- REST API data sources – Now display as their own data source type (previously nested under Bulk Query sources)
What’s new
- Field selection on all sources – Improve run performance by selecting only the fields the integration needs
- Restrictions on all sources – Apply filters even when the source connector doesn’t support it natively
- Calculations on all sources – Add calculated columns across all source types
- Preview with Log – Save an API request log when previewing a data source for easier debugging
Gaps & deprecations
- Multi data source – Coming in a later release
Integration Building
The authoring experience (defining sources, mappings, and targets) keeps its familiar shape, but the new platform makes building faster and easier to visualize. You can edit drafts without touching the live integration, the editing screens are streamlined.
What’s the same
- The core authoring flow – The familiar steps still apply: define a source, map your fields, set a target, and schedule the run
What’s changed
- Flat integration editor – The integration edit screen now has a flat structure, giving better high-level visibility of the integration with fewer navigation clicks
What’s new
- Drafts – Build and edit an integration without affecting the live version, then publish when ready
- View-only mode – Open an integration in a non-destructive, view-only mode
- Restrictions & calculations on all sources – Apply filters and calculations at the source level, even when the underlying connector doesn’t support them natively
Processing, Monitoring & Troubleshooting
How integrations run, how you monitor them, and how you troubleshoot failures are among the most substantial improvements. Distributed processing improves performance and scalability, while simplified logging, real-time monitoring, and richer run-level detail make it easier to see what’s happening, cut down on noise, and trace a failure back to its cause.
What’s the same
- Integration run methods – Manual, Scheduler, Realtime, and API
- Integration log tables – The same log tables remain available for reviewing run history
- System events – System event tracking carries over
- Error processing – Error handling options on your integrations carry over
What’s changed
- Microservice-based engine – The SmartConnect engine now runs integrations on distributed processing, allowing it to scale
- Simplified error details – System events and run histories now open in a drawer, with all events folded into a single record
- Configurable failure notifications – Batch failed-run notifications instead of receiving one email per failure, so high-frequency integrations don’t overload your inbox
What’s new
- Current runs – Real-time visibility into ongoing integrations across all users and run methods, so you can spot failing or stuck integrations without waiting for an email
- Notifications pane – Real-time notifications of errors throughout the system
- Destination lookup caching – Cache lookups at runtime to reduce API calls and improve performance
- API request log on the data source – Inspect the actual requests and responses for easier debugging
- Audit trail – See who changed what and when, so you can tie a failure back to a recent configuration change
- In-app contextual help – Guidance for the specific area you’re working in
API & Connectivity
The new platform is built to be managed programmatically and used by AI tools. The existing API has carried over, with a more powerful API, MCP server support, and a revamped Excel add-in arriving throughout 2026.
What’s the same
- Swagger-based API The existing Swagger-based API has been carried over to the new platform
What’s coming soon
- Full API – CRUD and OAuth support for programmatic management of integrations (July)
- MCP server – Lets AI clients create, configure, and manage integrations directly (August)
- Excel add-in – A revamped add-in for executing and reprocessing your integrations from Excel (September)
Gaps & deprecations
- Legacy APIs deprecated – The older SmartConnect REST API (svc service) and SOAP API are no longer supported
- Existing Excel add-in – The current Excel add-in does not support the new version, as it relies on the deprecated APIs
Connectors
Dynamics 365 Business Central
The BC connector is essentially the same in the new platform, same connector, same functionality. The one new capability is support for custom APIs as realtime data sources.
What’s the same
- Same connector and same functionality as SmartConnect.com
What’s changed
- Dynamics NAV is no longer supported, only Business Central online and on-premises
What’s new
- Custom APIs as realtime data sources — the BC connector now supports custom APIs as a realtime source, beyond the standard v2 APIs
Gaps & deprecations
- Dynamics NAV 2016 and older is no longer supported, only OData V4 compatible NAV instances are supported via the Business Central connector
Migration notes
- OData v4 page-based integrations will need to be rewritten within the next year. Plan to move these to API page-based integrations as part of the migration.
Microsoft SQL Server
The SQL Server connector carries over with full parity, same source and target functionality, same supported options. The one notable change is under the hood: realtime data sources now use the new Realtime Staging model.
What’s the same
- Same source and target functionality
- Still supported as global lookup column and task
What’s changed
- Realtime data sources now use the Realtime Staging table model
Migration notes
- Migrations should be straightforward for this connector
Flat Files (FTP, OneDrive, SharePoint)
These remain separate connectors in the new platform, as in SmartConnect.com. File formats and the supported file locations carry over. The two things to know: integrations can no longer run off a file uploaded directly to SmartConnect, and XML destinations have been overhauled.
What’s the same
- Same supported formats: text file, Excel, XML, and JSON
- Same folder location options: load from FTP, OneDrive, SharePoint, or Teams
- Same licensing implications (all file based connections only count against 1 licensed connection)
What’s changed
- Integrations can no longer run off a file stored in SmartConnect; you must either select a file at runtime or load it from a connection (FTP, OneDrive, SharePoint, Teams)
What’s new
- XML targets overhauled to support more complex XML structures
Migration notes
- XML data targets may not migrate successfully due to the new tooling
- Flat file data sources that ran off a stored file will become “select file at runtime” sources after migration
Popdock
The Popdock connector exists in both SmartConnect.com and the new platform, and the behavior is identical.
What’s the same
- Behavior is identical to SmartConnect.com
Migration notes
- Migrations should be straightforward for this connector
Generic REST
This is the same REST Services connector, and existing connections can be imported into the new version. It’s one of the more substantially enhanced connectors: target building is streamlined, source options are richer, and there’s new support for child linking and easier debugging. Note that XML targets and webhooks are not supported yet.
What’s the same
- Same REST Services connector — existing connections can be imported into the new version
- Still supports JSON and XML responses
What’s changed
- Sources
- Can now load fields from an API call (in addition to the existing load-from-JSON-file option)
- REST API data sources now display as their own data source type (used to be nested in Bulk Query sources)
- Targets
- A streamlined Structure builder replaces the separate Fields and Body tabs — the JSON payload is now defined together with the fields, for faster and easier builds
- Can now load the structure from an API call (in addition to the existing load-from-JSON-file option)
What’s new
- Child linking (up to 5 levels) — query child records based on a parent request (e.g. get a list of Orders (parent), then get order lines (child))
- API request log on the data source for easier debugging
- Data source restrictions filter data from a REST API on the SmartConnect side even when the API doesn’t support the filter natively
- Additional auth types: Bearer token and NTLM
- Field helpers on endpoint fields to insert variables easily
- Audit logs on REST Service configuration changes
Gaps & deprecations
- XML targets and webhooks are not supported yet
Migration notes
- Existing integrations should migrate well
- With the enhanced source options, some migrated integrations may be simplified, as more data can be collected and filtered at run time
Dynamics 365 Customer Engagement
The CE connector has been rebuilt on the REST API (replacing the old SOAP API). The core data sources remain the same, but target mapping now follows the OData model, so existing integrations will need to be rebuilt.
What’s the same
- Change and Realtime still driven by a CRM plugin
- Data sources still use FetchXML for a query builder experience
What’s changed
- Target mapping now follows the OData model instead of the SOAP based API, so target mapping will feel different
What’s new
- Support for multiple organization schemas — one connector can now handle differences between CRM environments
Gaps & deprecations
- Reference Lookups and Entity References are no longer needed in the REST API and have been merged into Entity Lookups
Migration notes
- Target mappings have changed significantly, so existing integrations will need to be rebuilt rather than migrated directly
Salesforce
The Salesforce connector is rebuilt on the REST API (replacing the old SOAP API). All three source types are supported, and OAuth is now the only authentication method.
What’s the same
- All three source types: Bulk, Change, and Realtime
- SOQL driven data sources
What’s changed
- Rebuilt on the REST API, replacing the old SOAP API
- Change data sources are now date filtered rather than Apex trigger based
- Destinations now only list each Object once rather than separate mappings for Update, Create, and Delete.
What’s new
- sObject listviews in Bulk sources in addition to SOQL queries
Gaps & deprecations
- Basic authentication is no longer supported
Migration notes
- Destinations are now restructured using the OData model and will work similar to the Business Central and F&O connectors.
- Sandbox and production now require separate connectors. They previously could be set up on a single connector, but now each needs its own.
Oracle NetSuite
The NetSuite connector is rebuilt on REST APIs with OAuth 2 support. The data sources available remain the same (SuiteQL, RESTlet, and Realtime), and REST destinations work as before.
What’s the same
- Same data sources: SuiteQL, RESTlet, and Realtime
- REST-based destinations unchanged
What’s changed
- Change data sources now use REST, previously used SOAP API
What’s new
- New Restlet-powered Saved Search data sources
Gaps & deprecations
- SOAP API is no longer supported
Migration notes
- SOAP-based integrations will need to be manually rebuilt using the REST-based connector
- REST-based integrations should migrate smoothly
Upcoming Connectors
More connectors arrive throughout the rest of 2026. The connectors below are on the roadmap and will be added to the new platform on a rolling basis. Target months are a guide and may shift, so reach out to eOne or your partner to confirm timing before you plan a migration that depends on one of them.
July 2026
Dynamics 365 Finance and Operations
Same functionality as the existing SmartConnect connector, connecting over OAuth and Integrates with your data through the OData and Data Management Framework (DMF) APIs
Dropbox
- Added as a file location for file sources and destinations, working the same way as the existing OneDrive and FTP options
Google Drive
- Added as a file location for file sources and destinations, working the same way as the existing OneDrive and FTP options
August 2026
Zendesk
- Dedicated connector built on the Zendesk REST API, with support for all three source types: Bulk, Change, and Realtime
PostgreSQL
- Added as a selectable database provider, so all SQL features (sources, destinations, lookups, and tasks) work with PostgreSQL just as they do with Microsoft SQL Server
MySQL
- Added as a selectable database provider, so all SQL features (sources, destinations, lookups, and tasks) work with MySQL just as they do with Microsoft SQL Server
September 2026
HubSpot
- Dedicated HubSpot connector for reading and writing your CRM data, built on the HubSpot REST API with OAuth 2.0
Shopify
- Dedicated Shopify connector built on the GraphQL Admin API, Shopify’s go-forward standard, so your integrations are built to last
Dynamics GP
- GP connector powered by eConnect, available from both the on-premises and cloud deployments of SmartConnect (the cloud deployment reaches on-premises GP through a gateway)
October 2026
SAP Concur
- Dedicated connector for Expense and Payables integrations extract approved expense reports and invoices into your ERP, and sync master data back into Concur
November 2026
Microsoft Fabric Lakehouses
- Write data directly to Microsoft Fabric Lakehouses using Open Mirroring
Google Sheets
- Add Google sheets as an API connector presenting tabs as table like sources and destinations
SharePoint Lists
- Add SharePoint lists, with each list acting as a typed, table-style data source or destination
December 2026
DataBlend
- Use DataBlend Collectors, Queries, and Data Targets within SmartConnect
If you have questions reach out to support@eonesolutions.com for assistance
