Skip to main content

ChapterSage Connection

Chapter 14 — From A to Z: taking over LUMEA DESIGN

Cabinet Méridien Conseil takes over the accounts of its client LUMEA DESIGN, kept in Sage 100. Here is the whole journey, with the figures of this book's screens.

In this chapter

  • Prepare: agent, server, database, mappings
  • Extract and check
  • Sync and verify
  • The next month: run again
  1. Agent
  2. SRV-COMPTA
  3. LUMEA_DESIGN
  4. Extraction
  5. 2025 closed
  6. 2026 open
Book contents

The starting point

LUMEA DESIGN keeps its accounts in Sage 100 for SQL Server, on its office server. The firm has opened its accounting file in IntegraSys, with a 2026 fiscal year in progress. It wants to take over 2025 and 2026 there, without retyping anything.

Install the agent

In Local agents, the firm clicks Add an agent, names it « Agent LUMEA DESIGN » and copies the server address and the token. It downloads agent-setup.exe, puts it in a folder on the client's Sage server, starts it, pastes the token, ticks Démarrer automatiquement avec Windows and clicks Démarrer.

Straight away, the agent's card shows Online, Version v1.12.4, and one server (chapter 2).

Declare the server

In SQL servers, the firm adds « SRV-COMPTA »: Via local agent — Agent LUMEA DESIGN, Server (TCP / instance), the server's host, the SAGE100 instance, the ODBC Driver 18 for SQL Server driver, and a read-only SQL Server account, integrasys_lecture. It saves, opens the server again and clicks Test connection: « Connection successful ». Show databases shows the LUMEA_DESIGN database (chapter 3).

Assign the database

In Client databases, it chooses SRV-COMPTA and the source software Sage 100 (SQL Server), clicks Refresh databases, picks the client LUMEA DESIGN on the LUMEA_DESIGN row, leaves All fiscal years and clicks Assign (chapter 4).

Check the mappings

In Mappings, on Sage 100 (SQL Server), the four cards carry Sage's standard names: F_COMPTEG, F_COMPTET, F_JOURNAUX, F_ECRITUREC. The client's installation is standard: nothing to change (chapter 5).

Extract and check

On the database's row, Extract opens the Extraction screen on LUMEA DESIGN (LUMEA_DESIGN). The firm keeps Accounting and All fiscal years (2025 and 2026), clicks All for the four data sets, and runs.

Progress ends on Succeeded: « 4/4 sets · 1 135 rows · 00:00:41 ». The detail:

Data setRows
Plan comptable603
Plan tiers7
Journaux5
Écritures comptables520

Under the entries, in green: « Check: 520 line(s) — every entry extracted » (chapters 6 and 7).

Sync

The firm clicks Sync to Accounting. The file had no 2025 fiscal year yet: the year's card said so, and a click on Create fiscal year 2025 created it, then restarted the takeover. In the end, both fiscal years are taken over:

Fiscal yearSummaryFate of the fiscal year
Exercice 202582 entries · 259 lines — « Every entry was taken over. »« Prior financial year: closed after the synchronisation. »
202683 entries · 261 lines — « Every entry was taken over. »« Financial year left open — exercice en cours (2026) : laissé ouvert. »

All 520 entry lines are there: 259 + 261. The missing accounts, third parties and journals were created; the vouchers are validated, under their Sage number (chapter 8).

Verify

Under the 2025 fiscal year, Reconcile Sage ↔ GL answers: « Balanced — the GL matches Sage. ». In the file's accounting, the Activity log keeps one sync line per fiscal year, and the 2025 closing line.

The next month

LUMEA DESIGN keeps keying in Sage. The firm runs a new extraction of 2026, then Sync to Accounting: unchanged vouchers are counted « Already synced », new ones are created, those Sage changed are updated, and those the firm corrected in the meantime are not overwritten (chapter 10).