Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
OpenUtilities
  • Product Communities
OpenUtilities
OpenUtilities Wiki Migrating Legacy Data To promis.e
    • Sign In
    • +OpenUtilities
    • Access Service Request Manager
    • Design Features - promis.e Functionality - Promis.e Standard
    • +OpenUtilities sisHYD Multi Utility
    • +OpenUtilities sisNET - English
    • +OpenUtilities Substation
    • Promis.e Paths
    • -Promis.e Wiki
      • +CONNECT Edition - Promis.e
      • About Promis.e
      • +Administration Features - Promis.e
      • +APIs_VBA - Promis.e
      • +Automation Features - Promis.e
      • +Component Features - Promis.e
      • +Component Management - Promis.e
      • +CONNECT Services - Promis.e
      • +Data Manager - Promis.e
      • +Database Platform Support - Promis.e
      • +Display - Promis.e
      • +Drawing Management - Promis.e
      • +Engineering Design Considerations - Promis.e
      • Error - Object reference...General
      • +Find_Replace - Promis.e
      • Finding the Tutorial
      • +Installation_Configuration - Promis.e
      • +Interoperability - Promis.e
      • +Licensing - Promis.e
      • +Maintenance Features - Promis.e
      • -Migration - Promis.e
        • Error - "An error occured when saving" opening pages of migrated project
        • Error - "An error occured when saving" with New Page
        • Error - Source catalog is not an ACAD catalog
        • Migrate a catalog from promis.e V8i Standalone to promis.e for AutoCAD
        • Migrating Legacy Data To promis.e
        • Migration Tips and Tricks
        • Migration Wizard
        • Moving From Promis.e for AutoCAD to Promis.e Standalone
        • Symbols from other catalogs appear in migrated catalog
        • Text alignment changes from Bottom to Descender
      • +OS Support - Promis.e
      • +Panel Layout - Promis.e
      • +Performance - Promis.e
      • +PowerPlatform Support - Promis.e
      • +Print_Publish Features - Promis.e
      • +ProjectWise Integration - Promis.e
      • Promis.e Help file
      • +Reports_Output Features - Promis.e
      • +Template Management - Promis.e
      • +Text Tools - Promis.e
      • Training FAQs
      • +Wire Numbering - Promis.e
      • +Wiring Features - Promis.e
      • +Project Management - Promis.e
      • Promis.e Title
      • Working from home with Promise.e
    • Replace Family - Find_Replace - Promis.e
    • SQL Server Login

     
     Questions about this article, topic, or product? Click here. 

    Migrating Legacy Data To promis.e

      Product(s): promis.e V8i
      Version(s): through 08.11.12.137
      Environment: N/A
      Area: Migration
      Subarea: N/A

    Background

    Once you install the new promis.e V8i version, you will probably want to be able to use your existing customized legacy data in the new version. This is done in various ways, depending on the version you are starting from. If you do not have custom data, then you should be able to use the standard built-in symbol catalogs and page formats, etc. You only need to migrate things that you have changed from the original. A general rule is that you should migrate all supporting items, like catalogs and page formats before you migrate the projects. If you do not, then you could get inconsistent results. 

    promis.e V8i SELECTseries 7 (08.11.12.137) is the last version to include the ability to migrate data from promis.e 5.0x, Aero, and Aero II.

    Migrating from promis.e 2007 version 3.x

    If you have promis.e 2007 3.0.1 - 3.0.3, you have the option of doing an upgrade install of promis.e V8i over your existing version. If you choose this option, then there is nothing to migrate, as the upgrade install does it for you. You should be able to simply open your existing projects and begin working.

    If you do a new install of promis.e V8i instead, or are switching from an AutoCAD based version to a MicroStation-based version, then you do have to migrate your legacy data. For projects, this consists of using the Project Manager to back up the existing projects in the legacy 2007 3.x version (be sure to check the box to save in MicroStation compatible format if switching to that version) and then restore them in the new promis.e V8i version. (Note: you must use a V8i version of MicroStation or MicroStation PowerDraft to migrate projects. An XM or older version will not work.) For catalogs, you would only need to migrate them if you were switching from an AutoCAD based version to a MicroStation-based version. If you are, then you will need to use the Migration Wizard, and select the radio button for migrating from AutoCAD to MicroStation.

      

    Information on how to use the Migration Wizard can be found in the system manual or promis.e help dialogs. Page formats are also migrated using the same migration wizard setting. 

    Migrating from promis.e 2007 version 2.x

    To migrate legacy data from this version, you will need to use the Migration Wizard as described above, but this time select "From promis.e Version 2.0". You will need to use this wizard to migrate custom symbol catalogs, page formats and parts databases. Follow the steps in the wizard, or look in the system manual for help on this feature. To migrate projects from promis.e version 2.x to promis.e V8i, you should use the Project Manager to back up the existing projects in the legacy 2.x version (be sure to check the box to save in MicroStation compatible format if switching to that version) and then restore them in the new promis.e V8i version. (Note: you must use a V8i version of MicroStation or MicroStation PowerDraft to migrate projects. An XM or older version will not work.) If you are changing from version 2.x and also switching from AutoCAD to MicroStation format, then your catalog files will need to be migrated twice, once using the setting from v2.0, and then that resulting file will need to be migrated using the setting for converting from AutoCAD to MicroStation format.

    Migrating from promis.e AERO II, AERO, 5.06 or 5.05

    To migrate legacy data from any of these versions, you will need to use the Migration Wizard as described above, but this time select "From Legacy promis-e". You will need to use this wizard to migrate custom symbol catalogs, page formats, language files, parts databases, and projects. Follow the steps in the wizard, or select the Help button on the dialog for more information.

    Migrating from older versions of promis.e

    If you have projects that were created in older versions of promis.e than the ones mentioned above, then you will need to first update them to promis.e version 5.05 or 5.06, then you can migrate them as described above into promis.e V8i. Please contact your sales manager for questions with this.

    See Also

    Migration Tips and Tricks

    Moving From Promis.e for AutoCAD to Promis.e Standalone

      Original Author: Tani_S
    • promis.e
    • Migration
    • how to
    • en
    • SELECTsupport
    • Share
    • History
    • More
    • Cancel
    • Tani_S Created by Tani_S
    • When: Fri, Jun 26 2009 2:35 PM
    • Matt_P Last revision by Communities MVP Matt_P
    • When: Fri, Mar 31 2017 1:14 PM
    • Revisions: 17
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies