SurgeTK Release Notes - 09/08/2026

This release is about what a sync leaves behind. An advisor you take off a household in Zoho now stays off, Redtail Account As Of dates read correctly, and the Homework sheet prints as one page in surge packets.
​

Everything below is live for every firm and happens on its own. Nothing here asks you to turn something on.

Household advisors

Your Zoho Lead Advisor field is now the answer in both directions.

This section applies to firms that map a Lead Advisor field in their Zoho household mapping.
​

An advisor removed in Zoho is now removed in SurgeTK. Each household the sync reads is reconciled: the advisors Zoho lists are added, the advisors the sync applied earlier and Zoho no longer lists are removed, and the servicing advisor is repaired when it pointed at one of the removed advisors. The writing advisor is never changed by a reassignment in Zoho. The first sync after this release does the cleanup in one run.
​

Advisors you added yourself stay. An advisor SurgeTK has never seen in Zoho on that household is treated as yours and is left alone. An advisor Zoho has listed at any point follows Zoho, so make that change in Zoho rather than in SurgeTK. A name Zoho still lists is added back on the next sync.
​

Removing someone from your team clears their Zoho link. Removing a user, or taking away their advisor seat, now also clears the Zoho advisor name linked to them, so the sync cannot put them back on households. Linking a Zoho name to a different user moves those households, along with their servicing and writing advisor, to the new user, and a link that fails partway can be retried safely. Only users who hold an advisor seat are considered when a Zoho name links itself.
​

A mapping mistake cannot empty your households. If more than half of your assigned households would change advisor in a single run, the removals are skipped for that run, and a Deep sync applies them once you have confirmed the mapping and the linked names. If nearly every household comes back with an empty Lead Advisor field, no sync mode applies it, because that is a mapping problem rather than a real reassignment. When Zoho lists a name SurgeTK cannot match to a user, which is what a renamed picklist value or a brand new advisor looks like, the previous advisor is kept on that household until you link the name in the Unlinked Zoho Advisors list in Settings.
​

Removals need a complete view of the household. A firm whose households match Zoho by name gets removals from a Deep sync only; other runs add without removing. After any run that had to skip or hold a removal, the sync stops re-applying advisors to households outside that run, and starts again only after a full sync that applies everything it sees. A removal you make by hand therefore stays, including on a household Zoho no longer sends at all.

The sync shows its work. The sync history drawer has a new Household advisors card: advisors added, advisors removed, servicing advisors repaired, households Zoho now leaves with no advisor at all, and any links cleared, each with the name and the reason. Every changed household also gets an activity log row, so an advisor change made by a sync is as visible as one made by hand.

Redtail account dates

Account As Of dates read correctly. Redtail holdings carry an as-of date whose digit order depends on the feed that wrote it inside Redtail. Some feeds send the year first, others send the month first. Each date is now read by its own layout.
​

A date SurgeTK cannot read is left off instead of guessed. A value that does not spell a real day, or that lands before 1900 or more than a year from now, no longer reaches the account.
​

Accounts showing an incorrect As Of year correct themselves on the next sync. There is nothing to click. The next Redtail sync rewrites the date from the holdings it reads. The balances beside those dates were current the whole time.

Homework sheet

Page one prints as one page again. In surge packets and from the household Print button, the Meeting Notes box could run past the bottom of page one, push the Action Items table onto a page of its own, and leave a nearly empty page behind it. The sheet is now sized for one printed page on every path.
​

Downloads and Quick Preview were always correct. A report downloaded or emailed from the household page, and the surge Quick Preview PDF, printed correctly throughout. Only surge packets and the Print button were affected.
​

Packets built between August 30 and September 4 keep the split. A saved packet keeps the layout it had when it was saved. Regenerate any packet from that window to pick up the fix.