Upgrade TeleMagic to SalesLogix

Telemagic to SalesLogix Conversions

In here we discuss upgrading Telemagic to SalesLogix and introduce TeleMagic customers and AMPs to the tools they can use to convert from TeleMagic to SalesLogix. We also include our recommended methodology.

SalesLogix is a highly-customizable application that was designed and built to provide Customer Relationship Management to the small and medium enterprise. As such, the application is based primarily on the following fundamental entities:
Accounts, also known as companies,
SalesLogix Contacts (or individuals),
SalesLogix Opportunities,
SalesLogix Tickets,
SalesLogix Defects,
SalesLogix Marketing Campaigns,
SalesLogix History and Activities,

This document applies to SalesLogix version 5.x and higher (up to SalesLogix 7.5) and TeleMagic versions 3.x, 4.x, and 5.x.

Currently, SalesLogix supports the following databases.
Microsoft SQL Server 2000 and above
MSDE and SQL Express for remote users and remote offices only

Project Methodology

When considering migrating to SalesLogix from TeleMagic, one must consider: data import changes to the User Interface (UI), such as screens or views (tabs, data grids, etc.) reports and queries (analogous to filters in TeleMagic) Since this can be a complex undertaking, we recommend that conversion projects be implemented using the following phased approach:

Discovery and Planning Phase for Converting TeleMagic

The planning and discovery phase is critical to the success of the migration effort. Quite often, even the customer is unaware of the state and integrity of the data, since it may contain legacy data from many disparate sources, accumulated over an extended period of time. The tasks in the discovery and planning phase include the following:
Identify data sources determine data points
Determine primary TeleMagic entities (accounts, contacts, orders, etc.) and their relation to the core SalesLogix entities
Identify users and build SalesLogix users and teams
Identify TeleMagic reports to be replicated
Identify TeleMagic custom functions not supported in SalesLogix
Identify queries (filters) to be replicated
Set project schedule
Run complete TeleMagic Rebuilds and DBUtils with full printed reports to inspect the TeleMagic install for any integrity issues

Development Phase

In this phase, the organization runs SalesLogix in a test environment that is in parallel and separate from the production TeleMagic application. During this phase, the following activities will take place:
Modify SalesLogix Data schema (new user-defined tables and/or fields)
Modify existing SalesLogix UI or build a new SalesLogix UI (screens, tabs, data grids, menus, tool and navigation bars)
Establish SalesLogix environment, including a test system
Map and test data import
Rebuild reports, queries (filters), and views (screens)

Remaining Phases

The remaining phases include the standard project phases, such as Quality Assurance, pilot rollout(if appropriate), and general rollout. During this phase one of the most important activities is user training, where the differences and similarities between the two products are explained. The recommended approach is to focus on the similarity between the two applications, explaining how each product uses different tools or methodologies to obtain similar if not the same results.


Conversion Methodology

Before migrating data and converting users to SalesLogix, those involved must consider the SalesLogix user administration and security as well as supporting remote clients and data synchronization.

User Administration

In SalesLogix, user information includes user type, name, site code, title, the person the user reports to, and whether or not the user can access SalesLogix Support. For remote users, information also includes the assigned sync server, sync transfer profile, when the user last synchronized with the host, and the last file sent and received. All of this information is important for on-going system maintenance and overall performance. Sage does not provide tools to directly replicate TeleMagic users and security rules into SalesLogix. Setting up users, security, and team membership is done manually using the SalesLogix Administrator. For conversions, it is important to specify record ownership when data is imported using either the SalesLogix SIM function or a Scribe DTS. It is highly recommended that the teams be defined and ownership determined before importing legacy data. However, if this is not done in advance, a powerful territory realignment tool can be used to adjust ownership of data once in SalesLogix.

Security in the SalesLogix Sales Client

In SalesLogix Sales, security is based on account ownership. There are three levels of account ownership: User, Team, and Everyone (in SalesLogix there's also a system team "Everyone Read Only"). Individual Users comprise a Team. A special team called Everyone includes all SalesLogix users by default. At the User and Team levels of ownership in SalesLogix, a security profile dictates the userís rights relating to a particular account. The ability to view, edit, or delete an account, and information pertaining to an account (including contacts and opportunities), can be limited to a User or a Team. If an account is owned by Everyone, no security restrictions exist.

Remote Users

A key capability of SalesLogix is the ability for remote disconnected users and branch offices to work offline and synchronize their data on demand. Synchronization in SalesLogix is based upon Account ownership and subscription rules, i.e., the Account that is associated with the record. The SalesLogix Administrator, a SalesLogix Administrative user, or the user can specify the accounts the user can subscribe to, as well as establish the user's subscription rules. Hence, it is critical that when importing Account-related data such as Contacts, Opportunities, and Activities, the account ownership be established for the records. Both the SalesLogix Import wizard and Scribe Migrate provide this capability. Additionally, functions are provided for assigning the appropriate Account owner to the record before it is inserted into the database. Likewise, the SalesLogix SDK provides a set of APIs that can be used to manage the assignment of the Account owner. In SalesLogix, packets of synchronized data called TEFs, Transaction Exchange Files, can be exchanged through direct network connection, RAS, FTP, or email.

Data Import from Telemagic into SalesLogix

This section contains references to import tools and SalesLogix tools.



Portions of this document were taken from existing SalesLogix documents.

SalesLogix Database Schema Guide and Database Schema Diagram
SalesLogix Implementation Guide
SalesLogix Planning Guide
SalesLogix Advanced Features Guide
SalesLogix Developerís Reference
SalesLogix Workgroup Administration Help
SalesLogix Architect Help
SalesLogix Developers Network Portal

For a complete copy of this white paper:

Converting Telemagic to SalesLogix

Please contact Rocky Mountain CRM