Considerations Before Deploying Continuum (Update 243)

We’ve made solid progress over recent months with Continuum (Update 243), with Partners actively testing client databases, scripts, and custom modifications.

A question that has recently been raised is:

“Can we upgrade our clients to Continuum now?”

Below is our current recommendation.

Recommendation for Upgrading Sites to Continuum

The primary difference between 242 and 243 (Continuum) at this stage is the remote database technology architecture.

The broader core functionality enhancements within Continuum are scheduled for release in the near future. Once those are delivered, we will be in a stronger position for widespread upgrades from 242 to 243.

Our Current Position

1. New Sites
All new implementations should deploy Continuum immediately only in a Remote environment.

2. Existing Sites Experiencing Performance Issues
Sites suffering from performance limitations or hardware constraints should consider upgrading now — provided they move to a remote database environment.
(See caveats below.)

3. Existing Sites Wanting to Upgrade (But Not Urgent)
Sites running 242 that would simply like to migrate — but are not facing operational pressure — should delay upgrading until the next phase of functionality is released within Continuum.

Caveats – Moving an Existing Site to Continuum

At this stage, we only recommend upgrading existing sites where:

• The database will be deployed remotely on a cloud server such as Cassini Cloud, or

• The client’s own cloud infrastructure (e.g., Amazon Web Services or Microsoft Azure). In this situation if the Partner is offering a Remote Cloud server option (either themselves or from a third party) that Partner must have suitable AWS or Azure experience in the server setup and implementation.

Partner Requirements

Before proceeding with any live migration, the Partner must:

• Have comprehensive Continuum experience, including involvement in initial testing and rollout of Firebird 5.

• Be confident deploying Continuum setup files to end-user local machines.

• Understand how to migrate FR3 Form layouts (en-mass and individually).

• Understand how to migrate Graphical Views and Workflows (en-mass and individually).

• Have already migrated a 243 copy of that site’s database to the new environment for testing and eventual site sign-off before Go Live.

• Be fully acquainted with the new temporary accounting integration posting method, including:

  • Xero

  • MYOB

  • QuickBooks Online

  • MoneyWorks

• Have suitably qualified IT support available to configure the Email Service (e.g., Microsoft Graph or AWS SES).

Mandatory Testing Requirements

Prior to any live migration, the following must be completed and signed off by the site.

• Run the Verify Scripts routine in Ostendo to identify high-level incompatibility issues.

  • All issues must be resolved before proceeding.

• Full testing of:

  • All Custom Scripts

  • Any Custom Triggers

  • Any Custom Stored Procedures

  • Any Custom Views

  • (Any identified issues must be resolved before live migration.)

• Full testing of all Custom Reports. Ensuring all fr3 layouts have been migrated as expected. (eg: Recently it was determined that a site had modified fr3 files located in their base system reports folder, these custom layouts were not migrated as they had been placed in the incorrect folder on the old server. This showed up a problem when testing)

• Full testing of migration of all Linked Documents and images

• If the site uses Freeway:

  • The API must be installed.

  • Existing Freeway Solutions must be fully tested prior to live migration.

• All third-party integrations must be fully tested and issues resolved.

• Any Custom software in the previous environment that interacts with Ostendo must be fully tested and issues resolved.

• Full testing of email functionality and its interaction with the configured email service.

• Full testing of connection latency to ensure the user experience is positive.

• Load testing of server with multiple Ostendo users connected and processing to highlight any possible Server spec issues. 

Summary

Continuum (243) is ready for:

• All new sites requiring remote cloud databases

• Selected performance-constrained sites moving to remote cloud databases

However, for stable 242 sites not under pressure, we recommend waiting for the next release phase of core functionality before upgrading.

This staged approach ensures stability, protects client environments, and allows Partners to deploy Continuum with full confidence.