Sage CRM Server Move Local to Cloud

Overview

Azamba will prepare and transfer over your Sage CRM program files, database, and library to your new cloud server. We also update all file locations and update any relevant ERP configurations. 

Upon completion of the project, you will be able to access your current CRM system on the new server using a new URL safely and securely. The old in-house CRM URL will no longer be live.

Deliverables

• Complete checklists and prepare compatibility.
  • Identify and contact any third-party add-on solution vendors to ensure compatibility with upgrade.
    • It is important for the client to identify all key third-party add-on solutions and ensure that they are represented on the preparatory checklist document.
    • If third-party add-ons are not compatible, we need to identify workarounds or discuss alternative approaches.
• Install a blank instance of Sage CRM on the new server that matches the existing version and patch.
  • Download install files and patches.
  • Install in default location.
  • Configure CRM and IIS.
• Perform existing CRM system backups.
  • Create backups of the Sage CRM program files, registry, and library.
• Copy files.
  • Copy CRM program files, database, and library over to new web server.
• Update file locations.
  • Move the database, program files, license key, and library into the new file locations on the web server.
• Update ERP configuration to point to the new CRM URL (may be the public URL).

• Test all major areas and entities of CRM.
  • Provide and walk through Sage CRM Core Functionality Testing Roadmap
    • This covers core Sage CRM functionality including Company, People, Communication and Opportunity entities and related screens.
    • The primary Azamba representative and the client representatives will review all key areas of the system per the Roadmap to determine whether there are any functionality problems.
    • NOTE: It is critical that the client personnel are involved in this step and we require sign-off post-move.
• Compare the new environment against the current live environment.

Technical Requirements

Azamba will provide a complete Sage CRM Server Move checklist.

Below is a list of technical requirements we typically need to perform a successful Sage CRM Server Move.

• Server/Environment Information
  • Server software: must be compatible with existing version of CRM and new version of CRM (we will provide a compatibility matrix sheet)
  • Memory: must meet the minimum RAM requirements from Sage
  • Disk space: must meet the minimum disk requirements to run Sage without heavy disk paging or memory faults
  • Java: must use a version compatible with Sage CRM
  • Server Names/IP addresses
    • Existing CRM and SQL servers
    • New CRM and SQL servers
• Security/Access Information
  • VPN
    • Client/Installation instructions
    • File download locations
    • Username/Password
  • Windows permissions
    • Administrator level access
    • Access to FTP and HTTP sites and download files (install files for CRM).
  • Remote desktop connection
    • IP address or domain name of server
    • Administrator-level username/password on local machine and domain
  • CRM system
    • Administrator-level access
    • RDP rights on server
  • ERP system (if any)
    • Administrator-level access
    • RDP rights on server
  • CRM Server(s)
    • Admin-level access to CRM
    • E-mail server information (if sending e-mails through CRM)
    • All applications on the new CRM Server and SQL Server
    • Document/library file share locations
    • Compatible versions of CRM
    • Ability to download files through FTP and HTTP protocols
    • All license keys for CRM from current version to new version (get from Sage)
  • SQL Server(s)
    • Admin-level access to SQL Server
    • SQL Server instance name
    • CRM Database passwords must not start with any special characters
    • Need SQL Server Management Server installed on the SQL server as well as the CRM application server.
  • ERP Server(s)
    • Need admin-role username/password
  • General Information
    • IT department or IT firm (third-party) contact information
    • ERP reseller contact information
    • All applications or file shares (including locations) on the new CRM Server and SQL Server

Assumptions

Please read through the following assumptions before accepting this proposal as the assumptions will dictate working conditions and any deviations may result in Change Requests detailing changes to timeframes, fees, and scope.

• A CRM-compatible version of MS SQL Server (using mixed mode authentication) and MS SQL Management Studio will be installed and operational in cloud environment prior to project commencement. MS SQL Management Studio will reside on the CRM server as well as the SQL Server, if the two servers are independent.

• SQL Server installation and configuration are the responsibility of the client and must be complete prior to project commencement.

• IIS must be installed on the CRM web application server prior to the migration.

• Any ERP or other integrated systems are upgraded by client’s in-house IT staff or another consulting firm and are compatible with the current version of Sage CRM.

• Network / IT personnel will be available to assist with technical and environmental issues as needed.

• All server software/hardware, database software, ERP/other system integrations, and Exchange must be compatible with the current version of Sage CRM.

• Administrative level access will need to be provided to MS SQL Server, CRM, and the network domain.

• Any remote connection information (including VPN / RDP information) will be provided to Azamba prior to commencement of work.

• Any work not explicitly specified in the above tasks will be bid separately as a Change Request.

• Any errors or issues with the setup or environment will be bid separately as a Change Request.

• Domain name resolution / IP issues will not be handled by Azamba under this proposal.

• A dedicated IP address is expected to be pre-configured and ready for use in IIS on the new web server.