You are viewing limited content. For full access, please sign in.



Attaching Laserfiche 8 repository/databse to Laserfiche Server 10

asked on May 12



I am going to be performing my first Laserfiche migration.  I have been reading the white papers and have a fairly good understanding of how to do this.  My client has a very old Windows Server 2003 server and is running Laserfiche 8.  The new server will be running Windows Server 2012 R2 and SQL 2012.  


I was wondering if I install Laserfiche 10.4 on the new server, will I be able to add the Laserfiche 8 repository to it via the repository wizard?  I know you can do an in-place upgrade from Laserfiche 8 to 10.4 but I can't seem to find if you can add a Laserfiche 8 database + repository to Laserfiche server 10.  If not, I am assuming I will have to upgrade LF8 to LF9, then migrate it over to the new server and then upgrade to Laserfiche 10.4.


Thank you for your help.  


- Jay 

0 0


replied on May 12 Show version history

Yes, basically go ahead and attach the repository to 10.4 as if it was already a current-version repository and it will proceed with the update. Make sure to use a backup of the repository database just in case - the process has been run thousands of times, but it's still a lot of database manipulation steps. The volumes are untouched but you'll need to remap them following the migration if the relative location has changed. 

Updating from Laserfiche 8, 9, or 10.x to Laserfiche 10.4 should have more information. 

Added: That said, Server 2012 R2 is a 10 year old OS. It is supported, but if you are doing an upgrade anyway... As for SQL 2012, be aware that is no longer supported in the current (v11) version of Laserfiche: End-of-Support Announcement for Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2, Microsoft SQL Server 2012, Microsoft SQL Server 2014 prior to Service Pack 3, SQL Server 2016 and SQL Server 2016 Service Pack 1 - Laserfiche Answers

1 0
replied on May 16 Show version history

Microsoft Extended Support for Windows Server 2012 R2 ends Oct 10, 2023. If you're going to the trouble to migrate, I would at least attempt to talk the client into punting the problem more than a year and a half down the line. That could be by either going to Windows Server 2022 and SQL Server 2019/2022 and worrying about it again in five to ten years, or by seeing if it's viable to migrate the client to Laserfiche Cloud instead and never worrying about it again.

I don't know if your client has to maintain cyber liability insurance as a condition of doing business, but if they do, they should know that insurers are being much stricter about things like running out of support operating systems and are either charging higher premiums or refusing to issue policies altogether until those systems are brought up to date.

1 0
replied on May 17

Thank you Samuel. 

0 0


replied on May 12

I can add that I could not get the SQL 2019 installer to upgrade SQL 2012 unless you happen to be on 2012 SP3. Then I ran into a problem with the old SP3 installer from Microsoft too. Without an upgrade path it might need a fresh install.

0 0
replied on May 13

Thank you both for your answers, this is great news.  

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.