The end of the year is usually about wrapping things up. This quarter, we're also starting something. A new interface, a redesigned integration engine, and a cloud-ready platform arrive in Q4, and we wanted you to hear about it here first.
Inside: a first look at the new release, highlights from our dev team, a year-end data checklist, platform updates, and a few ways to get involved before launch. Thanks for another year as part of the Sesame Software community.
— The Sesame Software Team
In This Issue
01 — The Revamp
For 30+ years, our focus has been giving enterprises complete control over their data. The Q4 release keeps that promise and rebuilds the experience around it: a modern interface that gets out of your way, a redesigned engine that moves data faster and more accurately, and a cloud-ready foundation built to scale.
Fast, responsive, and easier to use. Everyday tasks take fewer clicks and less waiting.
More reliable, efficient replication and ETL processing, so data moves between systems faster and with better accuracy.
More flexibility in how the platform is deployed and scaled as your needs grow.
Rolling Out
[Date or window]
Who Gets It
[All customers / by tier / phased]
What You Need to Do
[Nothing / upgrade / opt in]
Today
The New Interface
02 — From the Dev Team
"The new version has a modern user interface built in ReactJS that is fast, responsive, and easier to use, so everyday tasks take fewer clicks and less waiting."
Under the hood, a redesigned data integration engine makes replication and ETL processing more reliable and efficient, so data moves between systems faster and with better accuracy. And the application is now cloud-ready, which gives us more flexibility in how we deploy and scale it.
— Nathan [Last Name], Senior Software Engineer
What the team is most excited about
01
A ReactJS interface that responds quickly and streamlines everyday tasks.
02
A redesigned engine makes replication and ETL more reliable and efficient.
03
A cloud-ready application brings more flexibility in how it's deployed.
[Optional caption]
03 — Meet the Builders
Every feature in this release started as a conversation, whether with a customer, in a support ticket, or at a whiteboard. Here are a few of the people who turned those conversations into code.
Nathan [Last Name]
Senior Software Engineer
[What Nathan worked on in the new release.]
"[Favorite part of the revamp, in his own words.]"
[Name]
[Title]
[What they worked on.]
"[Favorite part of the revamp.]"
[Name]
[Title]
[What they worked on.]
"[Favorite part of the revamp.]"
04 — Rollout Timeline
We know "coming in Q4" isn't a plan you can work around, so here's the schedule. We'll send a reminder before each milestone, so you won't need to track this yourself.
[Date]
You're reading it. Full details, FAQs, and early-access sign-up are live.
[Date]
A limited group gets hands-on with the new release and shares feedback directly with our dev team.
[Date]
The new release becomes available to all customers [on your current plan / by tier].
[Date]
[Or, if nothing sunsets: "There's no forced cutover. Move when you're ready."]
05 — What's Changing
A big release can make people nervous, so here it is plainly.
06 — FAQ
No. The new interface is built to make the tasks you already know faster, with fewer clicks and less waiting.
[Yes. Your replication and ETL jobs carry over to the new engine.]
[Explain the deployment options, and confirm that you still choose where your data lives.]
[Yes. The new release is available for both on-premise and cloud deployments.]
[No changes to your current agreement.]
Yes, that's what early access is for. Sign up below.
Have a question we didn't cover? Reach out to support@sesamesoftware.com.
07 — See It Live
Tour the new interface, see the redesigned engine in action, and bring your questions for Nathan and the team. Can't make it live? Register anyway and we'll send you the recording.
08 — Quick Poll
Your answer helps us decide what to cover first in the walkthrough and in future how-to content.
09 — Year-End Checklist
Last quarter we suggested getting your data house in order before Q4. Here's the checklist to do it, and a good way to get your environment in shape before you upgrade.
Teams grow, automations change, and new objects appear. Make sure your backup frequency and scope still cover what your business depends on.
A backup you've never restored from is an assumption. Run a test restore on a small set of records so you know how it works before you need it.
Check that what you keep, and for how long, lines up with GDPR, HIPAA, SOX, or CCPA requirements.
If production data flows into a warehouse or sandbox, make sure SSNs, payment data, and other PII are masked where they don't need to be visible.
Moving historical data out of your live system can cut storage costs and improve performance, while keeping it accessible when you need it.
10 — Platform Updates
[One or two lines on what changed and why it matters.]
[One or two lines on what changed and why it matters.]
[One or two lines on what changed and why it matters.]
[One or two lines. Full release notes are further down this page and in the customer portal.]
11 — 2026 in Review
While the new release was in development, we kept shipping.
[#]
Releases shipped
[#]
CVEs resolved
[#]
New or updated connectors
[#]
Support cases closed
Highlights along the way included JWT authentication for Salesforce connected apps, a new Snowflake PrivateLink template, expanded Google BigQuery append-only support, and continued security hardening across every release. Thank you for growing with us this year.
12 — Release Notes
A full log of fixes, improvements, and new capabilities across all connector combinations. Use the filters to narrow by version or source system.
| Source | Target | Found In | Fixed In | Notes |
|---|---|---|---|---|
| Google BigQuery | Google BigQuery | 6.3.0.20260505.1 | 6.3.0.20260617.1 | Removed the BigQuery SQL Legacy feature as it has been deprecated by Google. |
| Any | Any | 6.3.0.20260505.1 | 6.3.0.20260616.1 | Added increased LDAP logging and resolved a bug where users were not being saved. |
| Salesforce | Any | 6.3.0.20260519.1 | 6.3.0.20260615.1 | Updated code to resolve a bug to work with token refresh and Tomcat configured for HTTPS so that jobs complete after connecting to Salesforce connected app. Caveat: only one job at a time unless you disable "Enable Refresh Token Rotation." |
| Any | Any | 6.3.0.20260402.1 | 6.3.0.20260608.3 | Resolved the following critical vulnerability errors: CVE-2026-40973, CVE-2026-42402, CVE-2026-42403, GHSA-72hv-8253-57qq, CVE-2026-22748, CVE-2026-42404, CVE-2026-22745. |
| Salesforce | Any | 6.3.0.20260525.1 | 6.3.0.20260604.1 | Added the capability to connect with Salesforce via the external app with JWT authentication method. |
| Snowflake | Snowflake | 6.3.0.20260417.3 | 6.3.0.20260505.1 | A checkbox was added to enable/disable the Copy Into command for faster processing on initial loads. Updated the code to use RJSnowflakeWriter when CopyInto is disabled. |
| Salesforce | Oracle 19c | 6.3.0.20260417.3 | 6.3.0.20260605.1 | Modified code to cache columns in the DB Writer which eliminated extra calls from the DatabaseMetadata, giving a slight performance boost. |
| Salesforce | Oracle 19c | 6.3.0.20260417.3 | 6.3.0.20260505.1 | Record additions and updates are now accurately reflected upon job completion and are correctly displayed in the UI when batch is enabled. |
| Salesforce | Google BigQuery | 6.3.0.20260320.3 | 6.3.0.20260505.1 | Added Google BigQuery's append only functionality to getFormula / getFormulaGlobal. |
| Snowflake | Snowflake | 6.3.0.20260418.1 | 6.3.0.20260423.4 | New template made for Snowflake Privatelink connections. Adjustments were made to account for dual drivers for standard Snowflake connections and Privatelink Snowflake connections. |
| Any | Any | 6.3.0.20260404.1 | 6.3.0.20260414.1 | The dropTableGlobal command was changed to honor the restricted list when Objects Downloaded is set to Restricted. This will not remove the RJ metadata tables unless the config is set to restricted mode. |
| Any | Any | 6.3.0.20260404.1 | 6.3.0.20260409.3 | Fixed LDAP login and refactored the login code to use new Spring security patterns. |
| Salesforce | Oracle 19c | 6.3.0.20260322.1 | 6.3.0.20260404.1 | Modified the GetDeleted algorithm to grow the interval at a slower rate after hitting the 600,000 limit to avoid bouncing back and forth. |
| Any | Any | 6.3.0.20260327.4 | 6.3.0.20260404.1 | Changed how we poll the pools to keep track of the job's progress and whether a process is still running. |
| Any | Any | 6.3.0.20260327.1 | 6.3.0.20260401.1 | Updated jar file versions to resolve multiple CVEs: spring-security-web 6.5.9, io.netty_netty-codec-http2 4.2.12, io.netty_netty-codec-http 4.2.12, spring-webmvc 6.2.17. |
| Salesforce | Any | 6.3.0.20260317.1 | 6.3.0.20260320.3 | The code now handles the "exceptionMessage='Entity type does not support deleted'" for Salesforce objects where it is not supported. The product will now skip the getDeleted() call for that object and print a message at the info level in the logs. |
| Salesforce | Google BigQuery | 6.3.0.20260309.5 | 6.3.0.20260320.1 | The code was updated to utilize the Append Only option to handle delete operations when the error "InsertMode=Streaming is not compatible with bulk UPDATE/DELETE statements" is encountered. This feature requires the Append Only setting to be enabled. |
| Salesforce | Google BigQuery | 6.3.0.20260308.2 | 6.3.0.20260319.1 | Fixed the bug where the 'Append Only' setting was enabled but bypassed field exclusion for Google BigQuery. |
| Salesforce | Google BigQuery | 6.3.0.20260308.2 | 6.3.0.20260319.1 | BigQuery now uses a single statement when adding fields during schema creation or modification. The QueryPassthrough option must be set to true for this behavior. Logic was added to conditionally construct statements based on the QueryPassthrough flag value. |
| Salesforce | Oracle 19c | 6.3.0.20260312.2 | 6.3.0.20260317.2 | Now detect and catch the ORA-30926 exception (unable to get a stable set of rows in the source tables), execute a SQL query to remove duplicates, and retry the merge. |
| Salesforce | Oracle 19c | 6.3.0.20260312.2 | 6.3.0.20260317.2 | Fixed ORA-01858 and ORA-01722 errors caused by non-numeric characters in number fields. Field order was adjusted so date/datetime and number fields are positioned at the end of the statement to prevent invalid character and number errors. |
| Any | Any | 6.3.0.20260205.2 | 6.3.0.20260316.2 | Added a check to only apply the security check logic for already existing passwords when a password is present; otherwise moves on to the next part of the code. |
| Salesforce | Oracle 19c | 6.3.0.20260312.2 | 6.3.0.20260312.2 | Added code to drop RJTMP_ tables with -dropTable and -dropTableGlobal. |
| Salesforce | Any | 6.3.0.20260115.2 | 6.3.0.20260227.7 | Fixed an issue where concurrent logins set to 1 caused the code to bypass the -getAllGlobal check and perform a -get for each object instead. |
| Salesforce | Oracle 19c | 6.3.0.20260205.2 | 6.3.0.20260217.2 | Now uses the aliased column name in the RJ_Field table when building the RJTMP tables instead of using the Salesforce field name. |
| Any | Google BigQuery | 6.3.0.20260111.1 | 6.3.0.20260201.1 | The value for the property rjConnectionString was updated to reflect the new connection method. A new template will need to be generated, or an existing template updated to match the new URL format. |
| Any | Any | 6.3.0.20260125.1 | 6.3.0.20260127.1 | Trash can icons not visible in the UI have been replaced with the cancel symbol across: Manage Users, Template Wizard, Jar Upload, License Manager, Job Step Monitor, and Upload/Download Selection Criteria. |
| Salesforce | Oracle 19c | 6.3.0.20260120.1 | 6.3.0.20260124.2 | Added functionality to the getParallel command (and any other command leveraging the RJGetParallel59 class) for the Oracle 19c database. |
| NetSuite | Any | 6.3.0.20251113.2 | 6.3.0.20251226.2 | Logging: Changed NetSuite composite primary key incremental-download messages from ERROR to INFO to reduce false-positive alerts and log noise. |
| Any | Any | 6.3.020251204.2 | — | Four CVEs resolved. |
| Salesforce | DB2 | 6.3.0.20251204.2 | — | Updated the DB2 driver to a more recent release compatible with Java 17. |
| Salesforce | DB2 | 6.3.0.20251212.2 | — | Fixed DB2 SQL syntax for RJ History Tables. |
| Any | Any | 6.3.0.20250917.1 | — | Made a code change to allow no username and password when sending emails via RJ. |
| BYOD | Any | 6.3.0.20251015.1 | — | Added REST driver for API, FTP, and local files. |
| NetSuite Suite Talk | PostgreSQL | 6.3.0.20251028.1 | — | Resolved NetSuite to Postgres truncation issue. Updated table truncation logic to only truncate end characters. |
| Salesforce | Google BigQuery | 6.3.0.20250904.1 | — | Resolved Google BigQuery error during deleted call. |
| Any | Any | 6.3.0.20250908.1 | — | Multiple CVEs fixed. |
| QuickBooks | Any | 6.2.2.20250701.1 | — | QuickBooks driver updated to 25.0.9376. |
| Salesforce | Oracle Database | — | — | CVE updated as required. |
| Salesforce | DB2 | — | — | DB2 set command adds case sensitivity to the relationship table to ensure proper parent/child insert handling. |
| Salesforce | Google BigQuery | 6.2.1.20241226.2 | — | Updated BigQuery template with "Append Only" option. This setting treats all updates as inserts. |
| NetSuite CRM & ERP | SQL Server | 6.2.1-RELEASE.20240202.1 | — | Issue with what is being shown to the API in RJ. No need for case with Cdata. |
| Salesforce | Google BigQuery | 6.2.1.20241016.1 | 6.2.1.20241226.2 | Added an insert-only option. Updates are applied as new record inserts. To enable, check the "append only" checkbox on the BigQuery datasource. |
| NetSuite CRM & ERP | PostgreSQL | 6.2.1.20241111.1 | 6.2.1.20241205.1 | Improved Postgres handling of child tables for NetSuite downloads. |
| NetSuite CRM & ERP | PostgreSQL | 6.2.1 | 6.2.1.20241205.1 | Duplicate issue resolved for support case 00035484. |
| NetSuite CRM & ERP | PostgreSQL | — | 6.2.1.20241205.1 | NetSuite InternalID field has been changed to an integer. |
| Any | Any | — | 6.2.1.20241127.1 | 17 Common Vulnerabilities and Exposures have been addressed in both 6.2.1 and 6.2.2. |
| Salesforce | Snowflake | 6.2.1 | 6.2.1.20241126.3 | Resolved memory management issues that could occur during large loads to Snowflake. |
| Salesforce | Snowflake | 6.2.1.20240923.2 | 6.2.1.20241126.1 | Updated functionality of the Delete_Flag to be uniform across operations; added support for Audit on Snowflake. |
| Microsoft Dynamics CRM | Azure | 6.2.1 | 6.2.1.20241125.2 | Microsoft Dynamics template and driver updated. Allows more options for OAuth connections. |
| Microsoft Dynamics CRM | Azure | 6.2.1 | 6.2.1.20241125.2 | Driver updated. |
| NetSuite Suite Analytics | SQL Server | 6.2.1 | 6.2.1.20241120.2 | Enhanced NetSuite Suite Analytics reconnect logic. |
| NetSuite CRM & ERP | SQL Server | 6.2.1.20240815.2 | 6.2.1.20241111.1 | Behaviour updated — contact support for details on the new behaviour. |
| NetSuite CRM & ERP | SQL Server | 6.2.1.20240815.2 | 6.2.1.20241111.1 | Object fails with message: Get Extra Column Info for table failed for AdvInterCompanyJournalEntry_lineList. This may be expected depending on the object. Contact Sesame Support with questions. |
| NetSuite Suite Analytics | Any | 6.2.1.20240820.1 | 6.2.1.20241031.1 | Updated the output of the checkcount command to include tab separation between values for better output evaluation and processing. |
| NetSuite Suite Analytics | Any | 6.2.1.20240820.1 | 6.2.1.20241031.1 | New commands available for SuiteAnalytics: -getallforced and -getallforcedglobal. These commands process the object as if it is non-incremental by ignoring ID fields and dates. |
| Salesforce | SQL Server | 6.2.1.20230927.1 | 6.2.1.20241016.1 | Code updated to give error with Java Memory Error for the error catch and reports the correct information on the main screen. |
| NetSuite CRM & ERP | PostgreSQL | 6.2.1.20240723.3 | 6.2.1.20241007.1 | Corrects a naming convention error that occurred under particular circumstances with PostgreSQL. |
| NetSuite CRM & ERP | SQL Server | 6.2.1.20240716.3 | 6.2.1.20241007.1 | Handling for liberation of child table Journal Entry enhanced for variations and dumping to Reject file when appropriate. |
| Salesforce | MySQL | 6.2.1-RELEASE.20240429.1 | 6.2.1.20241004.1 | Logs updated to show objects that are excluded for upload. |
| Any | Any | 6.2.1.20230209.1 | 6.2.1.20240807.1 | The datasource SQL query feature has been hardened to follow datasource licensing. |
| NetSuite CRM & ERP | SQL Server | 6.2.1.20240716.3 | 6.2.1.20240801.1 | Hardening of data type handling for child records. |
| Any | PostgreSQL | 6.2.1.20230518.2 | 6.2.1.20240731.1 | ETL now only includes accessible tables; un-ETLable objects are no longer listed to prevent selection errors. |
| Any | Any | 6.2.1 | 6.2.1.20240719.3 | Updated logging for enterprise licenses; expiry date now prints in the log. |
| NetSuite CRM & ERP | Any | 6.2.1.20240424.1 | 6.2.1.20240714.2 | Time zone selection in UI simplified to a more concise list of options. |
| Any | Any | 6.2.1.20240712.1 | 6.2.1.20240712.1 | Logging now includes user counts for auditing purposes. |
| Salesforce | Google BigQuery | 6.2.1.20240513.1 | 6.2.1.20240710.1 | Corrected a deficit in metadata acquisition for BigQuery. |
| NetSuite CRM & ERP | Any | 6.2.1 | 6.2.1.20240628.2 | Child Liberation added for Azure SQL Server. |
| NetSuite CRM & ERP | PostgreSQL | 6.2.1 | 6.2.1.20240627.1 | Null pointer exception on fresh install corrected. |
| Salesforce | Snowflake | 6.2.1.20240229.2 | 6.2.1.20240627.1 | Special build version of working 6.2.1.20231212.1 with Snowflake enhancements from this year. |
| Any | Any | 6.2.1.20240404.1 | 6.2.1.20240528.2 | Applicable CVEs have been addressed by updating libraries in use. CVEs that cannot be addressed have been identified with communication provided. Vertica Driver updated. |
13 — Welcome to the Team
[Title]
[Short intro: what they do and what they bring to the team.]
[What drew them to technology and to Sesame Software.]
[One or two personal details: hobbies, interests, or a favorite piece of advice.] Welcome to the team, [First name].
14 — Get Early Access
We're opening a limited early-access group for customers who want to try the new release before everyone else, and help shape the final version with direct feedback to the team that built it.
Drop us your email and we'll reach out when early access opens on [date].
No spam. Just updates when there's something worth sharing.
15 — Holiday Support Hours
Our support team is available throughout the season, with adjusted hours on the dates listed. For urgent issues outside those hours, [emergency contact process]. For everything else, email support@sesamesoftware.com and we'll get back to you as soon as we're back.
| [Date] | [Hours or closed] |
| [Date] | [Hours or closed] |
| [Date] | [Hours or closed] |
| [Date] | [Hours or closed] |
16 — Your Opinion Matters
We're proud to be rated by real customers and we'd love to hear from you. Leave us a review and we'll send you a $100 gift card as a thank-you for your time.
Leave a Review → Get $100 🎁It only takes a few minutes. Your experience helps other enterprise teams make better decisions.
"Sync is mostly hands off and we will go months without having to log into the server or application for any kind of issues. When we do have issues, support is quick to respond and usually resolve issues within a single 1 hr session."
Verified User, Investment Banking
"I tried other solutions and this is by far the best and most flexible. Their support is OUTSTANDING if you ever have an issue or just need a little guidance. They really do stand behind the product and are very responsive."
Pete C., CIO
"Pricing, pricing, pricing. Sesame Software is feature rich with a low annual cost overhead."
Verified User, Transportation & Trucking
Every improvement in this release traces back to feedback from customers like you: a suggestion on a call, a detail in a support ticket, a review on G2. We read all of it, and it shows up in what we build.
Here's to a strong finish to 2026, and to what's next.
— The Sesame Software Team