Sage 100

 View Only

  • 1.  Migrate Companies Left behind during initial Migration

    Posted 01-05-2021 12:24
    Client migrated from v2017 18 months ago.  Currently on v2020.  During the initial migration, they opted to leave about 15 PR backup companies behind.  They are now asking about bringing some of those companies into v2020.  Can you simply run the migration over again and just bring select companies over?  Am concerned that this type of migration will wipe out existing v2020 company data.  Or can one just set up the company in v2020 and copy the MAS_XXX folder to the current install and just convert the data.

    All thoughts/suggestions are appreciated.

    TIA

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------


  • 2.  RE: Migrate Companies Left behind during initial Migration

    Posted 01-05-2021 12:32
    You don't want to re-run migration.  As long as the company codes are different, you may be able to just copy the MAS_### folders into 2020's MAS90 and run company conversion...  You'd have issues with misaligned UDF's (if there have been any changes), and you won't get system level settings like paperless records, but for archive company codes I doubt that's a concern.
    Or just set up MAS90 mode shortcuts to the v2017 path and let them access the data without converting to v2020.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 3.  RE: Migrate Companies Left behind during initial Migration

    Posted 01-05-2021 12:37
    I was going to say just the opposite.  You could run migration as long as you don't do VI Jobs and System Files.  The concern I would have is whether there are any tax groups in the archive companies that aren't in the production environment and did those come over in System File Migration.  If Not, those might cause a problem.  
    Backup the production first before attempting.  
    N

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 4.  RE: Migrate Companies Left behind during initial Migration

    Posted 01-05-2021 12:45
    I believe when you re-run migration, even without migrating system files, you still lose the SY_Company records (which throws out a number of things like user permissions). 
    Copying the folders is much safer because you know you're only affecting those company codes, not the system.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 5.  RE: Migrate Companies Left behind during initial Migration

    Posted 01-05-2021 13:19
    For clarity - I think your question is what impact this has on migrating a non-framework to framework payroll.

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 6.  RE: Migrate Companies Left behind during initial Migration

    Posted 01-05-2021 13:27
    Edited by Kevin Moyes 01-05-2021 13:28
    I did the folder copy (then convert) method for a similar project back in 2018... as recommended by Elliott @ Sage.  It was for pre-framework PR history being brought into an existing system with PR 2.0.
    ​Customer was sold (directly by Sage) an upgrade to Premium before PR 2.0 was ready (oops!), and we had to split the system for a couple years (legacy PR off in it's own corner...), then merge the history back after PR 2.0 was released.


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 7.  RE: Migrate Companies Left behind during initial Migration

    Posted 01-05-2021 15:15
    I am leaning toward creating the company in 2020, rename the MAS_xxx folder (empty tables), copy the v2017 MAS_xxx folder into v2020.  After crossing my fingers, convert the 2017 data.

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------

    Original Message


  • 8.  RE: Migrate Companies Left behind during initial Migration

    Posted 01-05-2021 16:39
    I have these notes about files to save during payroll re-migration. I don’t know if this is applicable here since only a single company is remigrated into existing companies

    At least it gives some info which files are used

    https://www.evernote.com/shard/s1/sh/7fdbeca6-f7fe-4f38-9a17-6fa695f93e70/ec7c6ca24ddd6fc6e1092ff32d42017d

    ---------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ---------------------------------



    Original Message


  • 9.  RE: Migrate Companies Left behind during initial Migration

    Posted 01-05-2021 17:24
    Thanks.  Not a big concern as this is a first time conversion.  My big concern is do no harm to the system files.  The company to be imported is just a prior year copy of the production company so the system tax code tables should carry forward for the most part

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------

    Original Message


Related Content