Upgrade Subscriber 2017-09-14T11:18:50+00:00

UPGRADE FAQs

What Versions of MISys SAE are supported for migration/import into MISys Manufacturing?
The newest version of MISys Manufacturing can import and convert data from MISys SAE Versions 5.4, 5.5 and 5.6.

What can I do ahead of time to insure the process is as smooth as possible?
MISys SAE and MISys Manufacturing use completely different database schemas and data relationships. There are also differences in the MISys Manufacturing business logic that facilitate many additional features available in these newer products.

We suggest you do the following prior to attempting to import MISys SAE data into MISys Manufacturing:

  1. Perform a data integrity check in MISys SAE and repair any problems found.
  2. MISys Manufacturing does not allow certain reserved characters to be used in primary key identifiers for Suppliers, Locations, Jobs or Items. These reserved characters include asterisk '*', percent '%' or question mark '?'. Check if any of these reserved characters are used.
    a. You can use the Change Supplier Numbers or Change Item Numbers functions in SAE to change Suppliers or Items to eliminate these reserved characters ahead of time to avoid errors.
    b. There is no automatic function to change Location or Job keys, you must find these and manually remove or change any use of these reserved characters.
  3. Check if you have deleted locations, suppliers, items or jobs that are referenced by POs or Manufacturing Orders as this will cause an error in MISys Manufacturing when migrating from SAE. You must either add back the missing location, supplier, item or job in SAE or delete any POs or Manufacturing Orders referring to these deleted objects prior to conversion.
  4. MISys Manufacturing does not support segmented accounting. GL Accounts in SAE used with segmented accounting in Accpac will migrate to MISys Manufacturing and work but will not show the segment separator. They will still properly map to GL Accounts in Accpac.
  5. Consider purging data you don't actually need to migrate to MISys Manufacturing. This will make the migration faster and reduce potential for errors. You should consider purging/deleting:
    a. Old Jobs
    b. Old Purchase Orders
    c. Old Manufacturing Orders
    d. Old Log (History) records
    e. Old Stock Movement data
    f. Old or obsolete BOM revisions
    g. Inactive Items
  6. Identify any customizations that might have been done that might have written data directly to the MISys SAE database. Such customizations may be an issue when migrating data.
  7. Make sure you have the latest service pack and hot fixes for MISys Manufacturing before attempting to migrate your data. The latest service packs and hot fixes incorporate improvements in the migration that will make it process faster and more smoothly.
  8. Contact MISys Technical Support to inquire about any potential known issues with your particular installation.

How long will the migration process take?
It depends on the size your MISys SAE database. Smaller databases can be converted in an hour or less but very large databases (e.g. millions of records) can take many hours. We suggest purging unneeded data prior to the migration to speed up the migration.

What do I do if I get an error during the migration?
The MISys SAE Import function in MISys Manufacturing will report the first critical error that it cannot automatically fix. You will need to fix the issue in the MISys SAE data before you can continue. The MISys SAE Import function in MISys Manufacturing will allow you to continue from where you left off so you don't have to start the import from the beginning again.

It is impractical for all possible errors to be reported first as most errors (e.g. a missing item record) will propagate many more errors and it will be difficult to identify the primary errors that actually need to be fixed.

What do I do about custom reports created for MISys SAE?
MISys Manufacturing has a similar set of standard reports to what was available in MISys SAE. Due to the significant database schema changes between MISys SAE and MISys Manufacturing, custom reports must be re-written for use in MISys Manufacturing. Please consult your MISys Business Partner for more information. If you do not have a business partner, MISys can recommend one in your area.