# How to Set Up Multi-Site Configuration in SyteLine > Source: https://netray.co/erp-help/syteline-multi-site-intranet-configuration > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SyteLine supports multiple manufacturing or distribution sites either as separate Site records within one shared database, or as fully separate databases linked through intersite transactions and, in CloudSuite Industrial, ION. Getting the site model right up front, shared versus separate master data, intersite transfer setup, avoids a painful data migration later. ## Kind advanced ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module System Administration / Multi-Site ## Query how to set up multi-site configuration in SyteLine ## Alternate Queries - syteline multi-site intersite transfer setup - how does syteline share item master across sites - syteline single database multiple sites configuration - csi multi-site intranet architecture ## Applies To SyteLine 8.x/9.x and Infor CloudSuite Industrial, supporting single-database multi-site and multi-database, multi-tenant, site architectures. ## Steps ### Plan and configure a multi-site environment **Items:** Decide between a single-database multi-site model, each site a Site record inside one SyteLine database sharing the same application instance, versus a multi-database model, typically used when sites need separate go-live dates, separate chart of accounts structures, or data residency requirements. In the single-database model, create the new Site record under System Administration and decide, IDO by IDO, which master data, items, customers, vendors, GL accounts, is shared globally versus maintained per site. Configure user default sites and site security so staff only see and transact against sites they are authorized for, since a poorly scoped multi-site setup lets users accidentally post to the wrong site. Set up intersite transfer transactions, intersite purchase orders or transfer orders, for inventory flow between sites, including intercompany accounting if the sites also represent separate legal entities. If using separate databases per site, plan the integration layer, ION BODs in CSI or custom integration on-prem, for whatever master data genuinely needs to stay synchronized, rather than assuming it will replicate automatically. Test cross-site reporting early; consolidated reporting behaves differently depending on whether you chose single-database or multi-database, and this is the requirement most often underestimated during planning. Pilot the new site with a small, real transaction set, a handful of orders and receipts, before full cutover, and confirm APS/MRP planning correctly respects site boundaries so demand from one site does not consume supply intended for another. ## Sections ### Single database vs separate database per site **Body:** A single database with multiple Site records is simpler to administer and supports sharing item, customer, and vendor master data natively, but every site is tied to the same SyteLine version, upgrade schedule, and downtime window. Separate databases per site give each site independence for upgrade timing and data residency, at the cost of building and maintaining an integration layer to keep shared master data consistent across them. ### Intersite transactions and intercompany accounting **Body:** When inventory physically moves between sites, that movement is recorded as an intersite transfer order or intersite PO/SO pair rather than a simple inventory transaction, and if the sites represent different legal entities the intercompany accounting setup, due to/due from accounts, transfer pricing, needs to be configured before the first real transaction, not discovered afterward during month-end close. ### Master data strategy: shared vs site-specific **Body:** Deciding which master data is truly global, a part number should mean the same thing everywhere, versus site-specific, a customer that only ever orders from one site, or site-specific item costing, up front avoids a painful cleanup project later. Get finance and planning involved in this decision, not just IT, since it affects costing, consolidated reporting, and how MRP and APS treat supply and demand across sites. ### Multi-site reporting and BI **Body:** Consolidated cross-site reporting is straightforward when everything lives in one database, but requires an explicit consolidation strategy, a SuiteAnalytics-style connect, a data warehouse, or ION Data Lake in CSI, when sites are on separate databases. Plan this as part of the initial rollout rather than retrofitting it once site two is already live and finance is asking for a combined P&L. ## Pitfalls - Treating multi-site as a purely IT decision and discovering after go-live that finance needed shared chart of accounts or consolidated reporting the chosen architecture does not support well. - Not scoping user site security properly, so staff can post transactions against the wrong site. - Underestimating the integration effort required to keep item and customer master data synchronized across separate databases. - Letting APS/MRP planning parameters default in a way that lets one site's demand consume another site's supply unintentionally. - Skipping a real pilot with live-like transactions before full cutover, so intersite accounting issues surface for the first time during month-end close. - Assuming intersite transfers behave like a normal warehouse-to-warehouse transaction instead of setting up the correct intersite transfer or PO/SO pair and intercompany accounts. ## Ai Angle For a multi-site rollout, ERPray can answer which IDOs and tables currently treat this master data as global versus site-specific by inspecting the live data dictionary, rather than someone manually checking each IDO's site-scoping property, which materially speeds up the master data strategy decision. Once live, it can also field why did this order pull supply from the wrong site questions by tracing the actual APS/MRP allocation instead of a planner reverse-engineering it screen by screen. ## Faq ### Can we add a new site without downtime to existing sites? **Answer:** In a single-database multi-site setup, adding a new Site record does not require taking existing sites offline, but any customization or integration testing for the new site should still happen in a non-production environment first, since a misconfigured new site can affect shared master data seen by every site. ### Do intersite transfers automatically handle intercompany accounting? **Answer:** The transfer transaction itself is supported natively, but the due to/due from GL accounts and transfer pricing setup have to be configured correctly for each site pair beforehand; the transaction posts to whatever accounts are configured, right or wrong, so verify the setup with finance before go-live. ### Is a separate database required for sites in different countries? **Answer:** Not necessarily for SyteLine functionality itself, but data residency regulations, differing fiscal calendars, or a desire for fully independent upgrade schedules are common reasons sites choose separate databases even when a single database would technically work. ### How does APS handle multiple sites? **Answer:** APS scheduling generally runs per site against that site's resources and constraints, so supply and demand at one site normally does not cross into another site's schedule unless intersite supply relationships are explicitly modeled, which is worth validating during setup rather than assuming. ### What is the biggest planning mistake in multi-site projects? **Answer:** Deciding the database architecture, single vs separate, based only on the initial two sites without asking how many sites, and how different from each other, the company expects to have in three years; that assumption is expensive to reverse once the first site is live on real transactions. ## Search terms syteline multi-site setup, syteline intersite transfer, csi multi-site architecture, syteline single database multiple sites, syteline site security configuration, intercompany accounting syteline intersite, syteline multi-site master data strategy, syteline consolidated reporting multi-site, syteline separate database per site, multi-site aps mrp syteline --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json