iSAMS: On-Prem to Cloud

[molitor]

Anyone moved their iSAMS from on-prem to the cloud(iSAMS Cloud SAS)? If so, wondered if you'd mind providing a bit of feedback on the process and also your experience now that you are on iSAMS hosted cloud.

 

We will def miss having direct access to the DB for queries, but also for triggers and direct DB updates. For example, power automate and SQL triggers used to fire emails or reports off when certain DB actions take place...... for example new Student or staff Created or archived. How do you achieve those kind of things if you don't have access to the cloud?

 

Any real downsides you've experienced with the cloud service compare to on-prem. And the same for the positives?

 

Many thanks

[vikpaw]

We opt for cloud first, and have done a few migrations from on-prem to cloud. Generally, it goes well - better for schools that weren't used to having deep links to the server, so defo worth planning out all the touch points and how you will manage them. The support team handle it all, and plan the transfer etc.

 

Generally, very happy with cloud, as it's hands-off.

 

Things to think about during migration - what URL do/will you use. Get it in place, DNS changes, certificates etc.

Config of bulk email via send grid if you've been doing it in-house.

Creation of any API keys that you'll need, both REST and BATCH. I'm pretty sure they don't just migrate existing ones, though i have cloned one instance cloud2cloud for test purposes and it kept the creds, but it was on the same host.

 

Not sure about triggers off the DB but you could get in another service, such as Salamander Software or similar to do that, or try to build something in-house with APIs, but both are more likely to be checking for actions on a schedule. Not sure if there are web hooks or triggers available via the API, but it depends on the specific ask. Quite doable though, using create dates, if nothing really needs to be truly live.

 

You can get access to the DB for report writing and any other query you want to build, so request that up front as it takes time, and you need to provide a fixed IP that will be accessed from, so having a proxy / VPN will help if you need this for more than one user. You use this for PowerBI and potentially even building triggers if you can schedule some outputs to be synced to another DB, though you may as well use the batch API if you can wait 24 hours.

 

Also, getting new API creds takes time, you have to log a ticket and it gets passed to the tech team. It is purportedly on the plan to allow users to create their own in the UI, but it's in a later phase of API system improvements.

 

Big advantage is getting updates just done for you. If you want, you can request to be in a try it first group, or a do-me-last group which is handy. Generally speed and reliability are good for us and a big boon, especially for home / remote access as you're not relying on school networking infrastructure.

[molitor]

I have a specific question related to new students. When a new student is enrolled in our admission system (Open Apply) their details are automatically sent to iSAMS via the API and a new student created in applicants. When this happens, I have a trigger that fires off emails to various stakeholders around the school. My question is, when we move to the cloud I will lose access to the DB.... any recommendations on how to achieve this?

[TechMonkey]

You don't have to lose access to the DB. You can still access it but only from one IP, usually your School internet IP. You need to get Support to give you the details. I access the DB for reporting.

One alternative is to go with something like Locker or Salamander, that access the API and pick out new starters and triggers a workflow. Sounds like Salamander would be better, as I have found it to be more flexible and able to accommodate more workflows. The other is to pay for an upgrade Power Automate license to access the API yourself and write a flow that monitors for updates and fires off a workflow.