Telescan Sample Migration Requirements
Telescan to CallShaper Migration
To provide a clear, representative preview of how your accounts will operate within CallShaper, we will need a sample set of your data.
Note: This initial export is for evaluation purposes only. A more comprehensive data migration will be required for your actual system cutover.
Step 1: Account Selection
Please select 5 to 10 of your largest and/or most complex accounts. This ensures we capture a realistic picture of your daily operations and complex workflows during this exercise.
Step 2: Required Fields
For the selected accounts, please gather and provide the following files:
AMR and Forms Backups: The most recent backup files beginning with AB (e.g., AB$2026APR16.dat) and FB, respectively.
AMR Text Extracts: From the SDM interface Tools menu, select Extract AMR-To-Text for your 5 to 10 chosen accounts.
Screen Text Extracts: From the same Tools menu, select Extract Screens-To-Text for those same accounts.
Script Files: All relevant, or all total, script files (.ssf extension) located in the scripts folder on your SDM server.
On-Call Database Schema: Using SQL Server Management Studio, please generate a backup of your On-Call database schema, which is typically named OnCall or OnCall2.
Step 3: Next Steps & Delivery
Secure Upload: We will set up a secure, shared Google Drive folder and send you the link to safely transmit these files.
Follow-Up: O We will reach out if we encounter any unique scenarios that require clarification.
Screen Text Extracts: From the same Tools menu, select Extract Screens-To-Text for those same accounts.
Need a hand? If you need any assistance locating these files or generating the backups, please let us know. We are more than happy to jump on a call and help you walk through it.
Contact Us
For questions or concerns about this AUP, contact us:
Updated August 2026