Skip to content
English - United Kingdom
  • There are no suggestions because the search field is empty.

How to move a client from Calmony over to agentOS?

For Calmony account holders who then become agentOS CRM clients and users

Please note this is an internal process for the Calmony and agentOS support team

Q: How do I convert a client from a Calmony banking instance to agentOS?

Converting a client from Calmony banking to agentOS requires running a backend migration script. You cannot do this yourself - you must contact Dylan Davies (CTO) as he's the only person who can run the conversion script.

To initiate a conversion, provide CTO Dylan with:

The date and time must be agreed in advance because the client will be locked out of their old Calmony banking login as soon as the migration starts. The client's data will be moved and converted to the agentOS system.

 

Q: Why can't I manually migrate clients from Calmony banking to agentOS?

Manual migration is extremely time-consuming, error-prone, and creates significant issues for the client. Manual migration would require you to:

  • Create a new company on agentOS
  • Manually create all landlord records
  • Import Griffin bank accounts
  • Manually import verification codes for each payee
  • Recreate all staff credentials
  • Lock the client out of their old account during the process
Our automated script handles all of this end-to-end in a single process. The script:
  • Moves all data across automatically
  • Converts all payee records to proper landlord and contractor records
  • Preserves all existing verifications
  • Disables the old Calmony banking account
  • Maintains existing login credentials (though the login URL changes)
  • Even with a small number of payees (e.g., 24), the manual process carries a high risk of errors and requires locking the client out whilst you work. Always use Dylan's script.

 

Q: What happens to the client during a Calmony to agentOS conversion?

During the conversion process:

Before migration:

  • The client uses their existing login credentials at banking.calmonyapp.com

During migration:

  • The client will be locked out of their account whilst the migration runs
  • Dylan's script moves all data and converts payee records to landlord and contractor records
  • All existing verifications are preserved
After migration:
  • The client uses the same login credentials as before
  • The login URL changes to login.agentos.com
  • The old Calmony banking account is removed/disabled
  • All payees are now properly structured as contractor and landlord records

You must inform the client in advance about the agreed migration time and the new login URL.

 

Q: How do I convert a client from agentOS to a Calmony banking instance?

Converting a client from agentOS to Calmony banking also requires Dylan Davies (CTO) to run the migration script. However, this is a downgrade with significant data implications that must be discussed with the client first.

To initiate a conversion, provide Dylan with:

Critical pre-migration checklist:

Before proceeding, ensure the client has:

  • Exported all necessary data from agentOS (reports, records, etc.)
  • Exported all media files (photos, documents, etc.)
  • Understood they will be locked out of agentOS after migration
  • Understood their agentOS data will be deleted unless they purchase a data hosting package

Important: The bank account will move to the Calmony platform and will no longer be accessible through agentOS. If the client purchases a data hosting package, they can access their agentOS data (reports, records, etc.) but the bank account functionality will only be available via the Calmony platform at banking.calmonyapp.com.

 

Q: What billing considerations apply when converting mid-month?

When converting a client between platforms mid-month, the client's billing will appear across both platforms for that month. You must inform Alex (Finance) about the conversion so they're aware of the dual billing.

To make billing cleaner in future, consider restricting upgrades/conversions to the 16th of each month. This eliminates partial months and dual billing.

 

How much notice does Dylan need for platform conversions?

Dylan ideally needs at least a week's notice, scheduled for when he's not on holiday. However, if the conversion is urgent, he may be able to accommodate shorter timescales - he's previously offered same-day or next-day conversions when necessary.

Bear in mind:

  • The migration requires an agreed date and time
  • The client will be locked out during migration
  • If done overnight without warning, the client has no advance notice

Always try to give Dylan reasonable notice and agree a time that works for both the technical migration and client communication.

 

Q: Who do I contact for platform conversions?

A: Contact Dylan Davies (CTO) - he's the only person who can run the conversion script. Provide him with the client's full URL and your preferred migration date/time.