Available in: Axsy Field Service, Axsy Public Sector, Axsy Retail Execution

Axsy Data Migration Tool

Axsy's Data Migration tool migrates the namespace of data records that are used by Axsy from their Summer '23 format to their Autumn '24 format.


WHO NEEDS TO DO DATA MIGRATION?

Only customers who have existing Axsy Summer '23, Field Service, Public Sector or Retail Execution orgs need to carry out data migration.


WILL I NEED TO DO DATA MIGRATION FOR FUTURE AXSY RELEASES?

Once you have migrated your data to Axsy Autumn '24, or if your first Axsy installation is with Axsy Autumn '24 (or later) then you will not need to migrate your data again in future Axsy releases.


Preparing to Use the Data Migration Tool

Managed Package and Permission Set

To access the Axsy data migration tool you must install the Axsy data migration managed package into the org where migration needs to take place. See this article for the current version. If you do not have the installation link, create a support ticket in your portal requesting the installation link.


You must assign the Axsy Data Migration permission set to the user that will perform data migration actions.


Recommended: Only assign the Axsy Data Migration permission set to a single System Administrator user in your org to avoid accidental duplicate use of the tool.


Avoiding Possible Data Migration Errors

Before using the data migration tool:

  1. To avoid errors relating to Order items with zero quantities, follow the steps in this Enable Zero Quantity Orders article
  2. To avoid errors relating to the creation of new records, ensure that there are no automations or validation rules preventing new records being created.

Launching the Data Migration Tool

Launch Axsy Data Migration from the Salesforce app launcher.

For details of what and when to migrate see the process steps article.


Records Migrated

Records that will be migrated depend on the variant of the org, see the sections below for details.

Field Service Orgs

Standard Objects with Custom Fields Used by Axsy

None


Flows

Flows that use either of the Axsy custom Flow components listed below must be migrated to the Autumn '24 namespace. 

  1. Signature Capture
  2. Smart PDF

After being migrated the Flows will no longer function in the prior Summer '23 namespace.

Flows that do not use the above Axsy custom Flow components do not require migration the same Flows will continue to work in both Axsy Summer '23 and Axsy Autumn '24.


Axsy Custom Objects

All of the records in the following custom objects used by Axsy are migrated into new objects with the new namespace

  1. App Config Version – snapshots of configuration and metadata used by the Axsy mobile app
    axsy__AppConfigVersion__c ➞ axsy_mobile__AppConfigVersion__c
  2. Plugin – Axsy runtime Plugins
    axsy__Plugin__c ➞ axsy_mobile__Plugin__c
  3. Plugin Version – Versions of Axsy runtime Plugins (related list content of the above)
    axsy__PluginVersion__c ➞ axsy_mobile__PluginVersion__c
  4. App Login Session – User, session ID, device details and app version information shown in the Axsy Events Console
    axsy__App_Login_Session__c ➞ axsy_mobile__App_Login_Session__c
  5. App Event – Axsy mobile app events as shown in the Axsy Events Tab
    axsy__App_Event__c ➞ axsy_mobile__App_Event__c
  6. Notification – User notifications
    axsy__Notification__c ➞ axsy_mobile__Notification__c
  7. Notification Status – Status of notifications for users (related to the above)
    axsy__NotificationStatus__c ➞ axsy_mobile__NotificationStatus__c
  8. Mobile Location – user mobile location tracking
    axsy_Mobile_Location__c ➞ axsy_mobile__Mobile_Location__c

Public Sector Orgs

Standard Objects with Custom Fields Used by Axsy

  1. Visit (Visit) object fields:
    1. Actual Visit Start Location – User geolocations coordinates captured at the start of a Visit
      axsy_emr__ActualVisitStartLocation__c ➞ axsy_mobile__ActualVisitStartLocation
    2. Actual Visit End Location  – User geolocations coordinates captured at the end of a Visit
      axsy_emr__ActualVisitEndLocation__c ➞ axsy_mobile__ActualVisitEndLocation


Flows

Flows that use either of the Axsy custom Flow components listed below must be migrated to the Autumn '24 namespace. 

  1. Signature Capture
  2. Smart PDF

After being migrated the Flows will no longer function in the prior Summer '23 namespace.

Flows that do not use the above Axsy custom Flow components do not require migration the same Flows will continue to work in both Axsy Summer '23 and Axsy Autumn '24.


Axsy Custom Objects

All of the records in the following custom objects used by Axsy are migrated into new objects with the new namespace

  1. App Config Version – snapshots of configuration and metadata used by the Axsy mobile app
    axsy_emr__AppConfigVersion__c ➞ axsy_mobile__AppConfigVersion__c
  2. Plugin – Axsy runtime Plugins
    axsy_emr__Plugin__c ➞ axsy_mobile__Plugin__c
  3. Plugin Version – Versions of Axsy runtime plugins (related list content of the above)
    axsy_emr__PluginVersion__c ➞ axsy_mobile__PluginVersion__c
  4. App Login Session – User, session ID, device details and app version information shown in the Axsy Events Tab
    axsy_emr__App_Login_Session__c ➞ axsy_mobile__App_Login_Session__c
  5. App Event – Axsy mobile app events as shown in the Axsy Events Console
    axsy_emr__App_Event__c ➞ axsy_mobile__App_Event__c
  6. Notification – User notifications
    axsy_emr__Notification__c ➞ axsy_mobile__Notification__c
  7. Notification Status – Status of notifications for users (related to the above)
    axsy_emr__NotificationStatus__c ➞ axsy_mobile__NotificationStatus__c
  8. Mobile Location – user mobile location tracking
    axsy_emr_Mobile_Location__c ➞ axsy_mobile__Mobile_Location__c

Retail Execution Orgs

Standard Objects with Custom Fields Used by Axsy

  1. Assessment Indicator Definition (AssessmentIndicatorDefinition) object fields:
    1. Smart Indicator Data – Smart Indicator Definitions that you have setup
      axsy_cg__SmartIndicatorData__c ➞ axsy_mobile__SmartIndicatorData__c

  2. Order Product (OrderItem) object fields:
    1. Discount – discounts applied during Order capture
      axsy_cg__Discount__c ➞ axsy_mobile__Discount__c

  3. Store Product (StoreProduct) object fields:
    1. Sequence Number – ordering of products used in Inventory Capture
      axsy_cg__SequenceNumber__c ➞ axsy_mobile__SequenceNumber__c 

  4. Visit (Visit) object fields:
    1. Actual Visit Start Location – User geolocations coordinates captured at the start of a Visit
      axsy_cg__ActualVisitStartLocation__c ➞ axsy_mobile__ActualVisitStartLocation
    2. Actual Visit End Location  – User geolocations coordinates captured at the end of a Visit
      axsy_cg__ActualVisitEndLocation__c ➞ axsy_mobile__ActualVisitEndLocation

Flows

Flows that use either of the Axsy custom Flow components listed below must be migrated to the Autumn '24 namespace. 

  1. Signature Capture
  2. Smart PDF

After being migrated the Flows will no longer function in the prior Summer '23 namespace.

Flows that do not use the above Axsy custom Flow components do not require migration the same Flows will continue to work in both Axsy Summer '23 and Axsy Autumn '24.


Axsy Custom Objects

All of the records in the following custom objects used by Axsy are migrated into new objects with the new namespace

  1. App Config Version – snapshots of configuration and metadata used by the Axsy mobile app
    axsy_cg__AppConfigVersion__c ➞ axsy_mobile__AppConfigVersion__c
  2. Plugin – Axsy runtime Plugins
    axsy_cg__Plugin__c ➞ axsy_mobile__Plugin__c
  3. Plugin Version – Versions of Axsy runtime plugins (related list content of the above)
    axsy_cg__PluginVersion__c ➞ axsy_mobile__PluginVersion__c
  4. App Login Session – User, session ID, device details and app version information shown in the Axsy Events Tab
    axsy_cg__App_Login_Session__c ➞ axsy_mobile__App_Login_Session__c
  5. App Event – Axsy mobile app events as shown in the Axsy Events Console
    axsy_cg__App_Event__c ➞ axsy_mobile__App_Event__c
  6. Axsy Assessment Task Order – Defines the order in which Assessment Tasks are performed
    axsy_cg_AxsyAssessmentTaskOrder__c ➞ axsy_mobile_AxsyAssessmentTaskOrder__c
  7. Notification – User notifications
    axsy_cg__Notification__c ➞ axsy_mobile__Notification__c
  8. Notification Status – Status of notifications for users (related to the above)
    axsy_cg__NotificationStatus__c ➞ axsy_mobile__NotificationStatus__c
  9. Mobile Location – user mobile location tracking
    axsy_cg_Mobile_Location__c ➞ axsy_mobile__Mobile_Location__c

Post Migration


YOUR EXISTING TRIGGERS AND PROCESSES

If you have triggers or other processes that use any of the Axsy Summer '23 industry variant prefixes these will need to be modified to use the axsy_mobile__ prefix after migration.