Announcement

Collapse
No announcement yet.

data migration best Practice for mm9

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    data migration best Practice for mm9

    All,

    Just curious how you guys are migrating products information from an old mm5 store to an mm9 store? Do you export products and then export attributes/option separately? Does anyone still use 'Import Products w/Variants From Flat File' and does this still work for mm9? How about Miva support? How does Miva do this for their clients?

    Thanks

    #2
    Re: data migration best Practice for mm9

    It somewhat depends on the complexity of the product data and the module involved. If you can use the product export to csv that is the easiest solution but that will not bring over any module related data.

    Right not we typically transfer tables at the database level.

    However we will be releasing a MMUI to CSSUI conversion tool that will allow you to change UIs on a store and keep all your data. You will need a dev store to do it and then you can build your new store in a dev environment, save the framework, and apply it to the live store.

    We're currently testing the new tool internally but it should be available soon.
    Brennan Heyde
    VP Product
    Miva, Inc.
    [email protected]
    https://www.miva.com

    Comment


      #3
      Re: data migration best Practice for mm9

      We're currently testing the new tool internally but it should be available soon.
      Wow! How soon is "soon"???

      Days?
      Weeks?
      Other?

      Thanks in advance.
      Mark Romero
      ~~~~~~~~

      Comment


        #4
        Re: data migration best Practice for mm9

        Thanks Brennan.

        In the meantime, I would like to keep things simple to continue building out the new store for testing purposes. So if i am interested in just the product information with its variant (omit 3rd party module data), Do you still recommend using product export to csv? Also, it might be a dumb question but I only see 'export product to a flat file' is that the same? On the import side, I do see 'add/update products from csv' and 'add/update product variant from csv'. Are there an export equivalent?

        Thanks

        Comment


          #5
          Re: data migration best Practice for mm9

          Mark,

          It should be available for testing/use next week, but with a giant caveat and Asterix. It's vital you make a backup before you use this tool, because it's possible to destroy your store with it.
          Thanks,

          Rick Wilson
          CEO
          Miva, Inc.
          [email protected]
          https://www.miva.com

          Comment


            #6
            Re: data migration best Practice for mm9

            Thanks for the update and the warning!
            Mark Romero
            ~~~~~~~~

            Comment


              #7
              Re: data migration best Practice for mm9

              I tried all the product export format but none of them linked the variants with the parent. Do I have to do this manually (click on generate variants)? Here is what I have done.

              cvs format for 1 product

              1. export products from flat file (variants records are included)
              2. export attribute and options (using Bills module)
              3. import products from csv
              4. import attribute and options (using Bills Module)
              5. manually click 'generate variants'

              xml provision format

              1. export product to flat file (xml provision format)
              2. export attributes to xml file
              3. import data and setting in xml provision format (both xml files)
              4. manually click 'generate variants'

              Comment


                #8
                Re: data migration best Practice for mm9

                Now that everything is in the new store I think you might need to do this but hoping Brennan can chime for you with more info
                http://extranet.miva.com/forums/show...ntory-variants
                Last edited by Mark Hood; 04-30-15, 12:08 PM.
                Mark Hood
                Vermont Gear

                Comment


                  #9
                  Re: data migration best Practice for mm9

                  Mark is correct. There is no way to built in export that will import in way that will create the variants. You either have to do it manually, to the thread he linked to can be used to generate a page of XML which can be imported to generate the variants for you.
                  Brennan Heyde
                  VP Product
                  Miva, Inc.
                  [email protected]
                  https://www.miva.com

                  Comment


                    #10
                    Re: data migration best Practice for mm9

                    Originally posted by Brennan View Post
                    Mark is correct. There is no way to built in export that will import in way that will create the variants. You either have to do it manually, to the thread he linked to can be used to generate a page of XML which can be imported to generate the variants for you.
                    Just to clarify because I think I know where he is stuck.

                    He actually already has all the products in the store already and doesn't need to "create the variants" because they already exist. He just needs the step of associating them with the master. Will the XML do this without messing up what he already has and is there a shorter version? Sorry Kit if I'm stepping on your toes :)
                    Mark Hood
                    Vermont Gear

                    Comment


                      #11
                      Re: data migration best Practice for mm9

                      Yeah it will work without messing things up. If the part product already exists, as long as you use the same delimiter as when they were originally created, running the XML will try to create the part product, see it already exists, skip that step and just do the remaining parts of linking everything up. This is assuming the variant part products codes are default and have not been changed from when they were originally created.
                      Brennan Heyde
                      VP Product
                      Miva, Inc.
                      [email protected]
                      https://www.miva.com

                      Comment


                        #12
                        Re: data migration best Practice for mm9

                        @Mark - Thanks and you are always welcome to step in as you can elaborate my issues better.

                        @Brennan - Appreciate the insight. Before I dive into this xml effort, do you know if I can use 'Import Products w/Variants From Flat File' ? It was a free module that was distributed to help us migrate to variants a while back. We still use it today to import new products on mm5. Just curious if it is still being supported. If not, xml it is.

                        Comment


                          #13
                          Re: data migration best Practice for mm9

                          That module does work and will create products/ attributes and variants from a csv file, however there is no export to export data in that format. It was only design for adding new products.
                          Brennan Heyde
                          VP Product
                          Miva, Inc.
                          [email protected]
                          https://www.miva.com

                          Comment


                            #14
                            Re: data migration best Practice for mm9

                            Any update on the MMUI to CSSUi tool?

                            Also, how is the best way for one to make a backup of their store just in case the conversion goes bad???

                            Thanks in advance.
                            Mark Romero
                            ~~~~~~~~

                            Comment


                              #15
                              Re: data migration best Practice for mm9

                              It'll be released this coming week.
                              Thanks,

                              Rick Wilson
                              CEO
                              Miva, Inc.
                              [email protected]
                              https://www.miva.com

                              Comment

                              Working...
                              X