Migration Overview

Jonathan Semones -

This document outlines the steps that you will need to follow in preparation for a migration.  The instructions provided here are based on Lucity's standard operating procedure for setting up the Lucity System.

Important! Migrating your system to new servers is a process that is not covered by Lucity Support.  We can provide information, and answer questions, but cannot do the process for you.  If you would like Lucity to do this for you then contact us and we will give you a quote.


  • What components are you moving?
  • This may be just your database or it may be your entire Lucity system.
  • What are the Lucity requirements?
  • Lucity System Design
  • Tech Specs
  • Where will the moving components go?

System Planning

  • Write down the Servers you will set up.
  • Write down the Lucity components you will install on each server.
  • If you are redesigning your entire system there are attached sample system designs. They are broken out in standard system designs and minimum system designs.  They are also broken out based on whether you will be using a DMZ server or VPN for Mobile

Standard System Designs

This is an example of the best way to setup Lucity on your network.  A design like this will allow for the greatest performance of the Lucity system.  You may not need all of the recorded elements depending on what parts of the Lucity application you use.

Note: These designs are attached at the bottom of the article.

Minimum System Designs

These are examples of a system design in a scenario with minimal resources.  A design like this will not work optimally especially if you have more than a few users.

Note: These designs are attached at the bottom of the article.

System Users

  • Several Lucity applications require Active Directory Users to run.  You can use your own AD users but the following are the standard ones that we use for our applications.
    • Lucitysvc - Lucity Services User.  This user should be used to run the Lucity Services.
    • Lucitydoc - Lucity Document Server User.  This user should be used to run the Lucity Document Server.

Lucity Hive Planning

Lucity stores shared components in various hives.  We have a standard structure for where an how these hives are setup.  Using our standard is helpful when working with support as it is easier for us to find the various components of your system.

  • LucityServer - Shared directory on the Network that contains all of Lucity's shared components.  All users must have Read/Write access to this Share.  Lucitysvc must have permission to read/write/modify/list/execute in this folder.  
    • DocShare - Stores all components that are managed by the Lucity Document Server.  Lucitydoc must have permission to read/write/modify/list/execute in this folder.
      • CitizenAppHive - Stores files for specialized citizen-facing applications.
      • CitizenDocuments - Stores documents that citizens have uploaded with requests.
      • CustomReports - Stores custom reports used by the web applications.
      • InternalDocuments - Stores documents that Lucity users have uploaded.
      • SignLibrary - Stores custom sign library images.
    • License - Stores the current LicenseCodes.xml.
    • Lucity - Contains the data configured by the Lucity Server install.  Most notably the Config folder.
    • LucityInstall - Stores the install media.



  • Pre-install checklist - Attached at bottom of article.  This is a document to prepare for a successful installation based on the agreed system architecture.  
  • Prepare locations where Lucity components will be moved to.
  • Setup Active Directory Users to run Lucity applications.  The suggested users are Lucitysvc to run services and Lucitydoc to run the document server.


Complete the install using the following resources


After a successful migration make sure you keep track of your Servers, users, and passwords.

Have more questions? Submit a request