Margin Master Handbook
- Prerequisites
- Firewall and Network Requirements
- Microsoft Edge Download Block
- SQL Server Authentication Setup for IT Administrators
- Antivirus and Endpoint Security Exclusions
- SQL Server Tools
- Install or Upgrade SQL Server Express
- Install or Upgrade SQL Server Management Studio
- A Tour of the Main Window
- The Menus
- The Button Row
- The Main Data Grid
- The Summary Section
- Banners and Badges
- The Options Window
- Store Configuration
- Miscellaneous
- Export Options
- Vendor Settings
- POS / Connections Tabs
- Background Service
- AI Assistant (Experimental)
- How POS Import Works
- Supported Point-of-Sale Systems
- Data Import Workflows
- RockSolid POS Import
- Epicor Eagle FTP Import
- Epicor MySQL Compass Import
- Transact POS Import
- Paladin POS Import
- Falcon POS Import
- Spruce POS Import
- Bistrack POS Import
- RockSolid Max POS Import
- ECS POS Import
- Prosperity POS Import
- Catalyst POS Import
- Westlake POS Import
- MI9 POS Import
- AS/400 POS Import
- CounterWorks POS Import
- Dimension POS Import
- PacSoft POS Import
- ProStix POS Import
- Sympac POS Import
- Propello POS Import
- EagleVision POS Import
- MySQL/Compass Connection Configuration
- ECI VPN Requirement (Spruce, RockSolid MAX)
- Propello POS Integration Guide
- MI9 Data Pipeline — Import to Main Table
- Troubleshooting: Epicor Import Brought In 0 SKUs
- PACE POS Import
- Advantage POS Import
- General Store POS Import
- J-3 POS Import
- KeyStroke POS Import
- AutBusSystem POS Import
- Tomax POS Import
- Enterprise POS Import
- Computakey POS Import
- Redisell POS Import
- DART POS Import
- MIB POS Import
- Substruct POS Import
- DMAS POS Import
- RODS POS Import
- Procom POS Import
- Agility POS Import
- Acumen POS Import
- Cruise POS Import
- LSandE POS Import
- Retalix POS Import
- DIBCorp POS Import
- GMROI POS Import
- ECi Advantage POS Import
- Sunray POS Import
- ActivantAutomotive POS Import
- IBS POS Import
- Versys POS Import
- RMS POS Import
- TAMS POS Import
- Integrasoft POS Import
- Dynamic POS Import
- Microsoft ARS POS Import
- CDS POS Import
- Spartan POS Import
- Nitterhouse POS Import
- Jeds POS Import
- Theisens POS Import
- Emery Jensen POS Import
- SMS Pro POS Import
- Burdens POS Import
- Intact POS Import
- Bloom Retail POS Import
- NCR Counterpoint POS Import
- Horizon POS Import
- Cloud Vendor Data Sync
- Data Aging and Freshness Warnings
- Resetting Vendor and POS Data
- Rebuild Data and Rebuild Selection Lists
- Troubleshooting Vendor Sync
- Understanding the Strategy Hierarchy
- Pricing Strategies
- Creating a Strategy Step
- Updating and Deleting Steps
- Reviewing a Strategy and Running It
- Shared (Premade) Strategies
- SKU-Level Exceptions
- Manage Custom Groups
- Strategy Execution Cloud Tracking
- Importing from Excel
- Cost Break Analysis
- Cost Break Strategies
- Min/Max Strategies
- Strategy Backup & Restore
- Add Items from Catalog
- Store Grouping
- Data Diagnostics and Missing Index Recommendations
- System Diagnostics
- Margin Master Cannot Save Settings
- SQL Server 2025 Express vs. Full License
- Support Issue Management
- Catalog Lookup
- What's New After an Update
- Version History
- Documentation and the Help Buttons
- CTLD — Do It Best Catalog File
- MARGIN_MASTER — Ace Catalog File
- PCDITEMXREF — Do It Best SKU Classification File
- SAP_ZONE_PRICE_MARGIN_MASTER — Ace Zone Pricing File
- PCDPRODCLASS — Do It Best Product Classification Hierarchy File
- SAP_STORE_DEPT_ZONE_MARGIN_MASTER — Ace Store Zone Assignment File
- Taxonomy — Ace Product Classification File
- Mapp_Pricing — Ace MAP & IMAP Pricing File
- margin_mstr_plano — Ace Planogram File
On This Page
Transfer Settings from Database
What is this?
Margin Master lets you copy your configuration -- pricing strategies, rounding schemes, views, and other settings -- directly from one database to another. When you create a new database or migrate to a new server, you do not need to re-enter all your settings by hand. The transfer reads settings straight from the source database over SQL Server, so no backup file is needed.
Who is this for?
- New database setup -- After creating a fresh database, quickly bring over your existing configuration instead of starting from scratch.
- Server migrations -- Moving to a new SQL Server? Copy settings from the old server's database to the new one in a few clicks.
- Store cloning -- Replicate one store's setup to another store's database.
- Recovery -- Restore settings after a database was recreated or reset.
How to Access
Automatic Prompt (After Database Creation)
- Create a new database via File > Database > Create Database.
- After creation completes, a prompt appears: "Would you like to copy settings from an existing database?"
- Click Yes to open the Settings Transfer dialog.
Manual Access (Menu)
- Go to File > Backup/Restore > Copy Settings from Database.
- The Settings Transfer dialog opens.
Step-by-Step Guide
Step 1: Select the Source Server
The SQL Server dropdown is pre-populated with servers from your known connections. You can also type a server name directly.
- Local servers appear as the machine name (e.g.,
DESKTOP-ABC123) - Remote servers use their full name (e.g.,
SQL-SERVER-01or192.168.1.100\SQLEXPRESS) - Windows Authentication is used to connect
Step 2: Select the Source Database
After selecting a server, the Database dropdown populates with all user databases on that server. System databases (master, tempdb, model, msdb) are excluded, and the currently active database is also excluded to prevent self-copy.
Step 3: Validation
When you select a database, the system validates it is a valid Margin Master database by checking for required tables:
ApplicationSettingsGlobalFileConfigPricingStrategiesRoundingSchemes
If validation fails, a message explains what is missing. Only valid Margin Master databases can be used as a source.
Step 4: Review Available Settings
Once validated, the system reads all transferable settings from the source database and shows a status summary, for example:
Ready -- found 3 strategy(ies), 5 rounding scheme(s), 42 app setting(s)
The familiar backup/restore checkbox panel appears with two columns:
Common/Typical:
- Pricing Strategies (with sub-checkboxes for Steps, Custom Groups, SKU Level Exceptions)
- Rounding Schemes
- Database Connections
- Views
- Sort Options
- Store Groups
Optional:
- Startup Checks
- Import Processing
- Database Settings
Checkboxes that show "NA" (strikethrough) indicate that section has no data in the source database.
Step 5: Select What to Copy
Check the settings you want to transfer. At minimum, most users will want:
- Pricing Strategies (with Steps, Custom Groups, SKU Level Exceptions) -- your pricing rules
- Rounding Schemes -- how prices are rounded
- Views -- your custom column layouts and sort orders
- Database Settings -- application preferences and feature toggles
Step 6: Execute Transfer
Click Copy Settings. The application:
- Writes the selected settings to the current database
- Reinitializes with the new settings
- Shows a success message
What Gets Transferred
| Component | Description |
|---|---|
| Pricing Strategies | Strategy definitions with all nested rules |
| Strategy Steps | Individual pricing rule steps within each strategy |
| Custom Groups | Named SKU groupings with their member SKUs |
| SKU Level Exceptions | Per-SKU pricing rule overrides |
| Rounding Schemes | All rounding rule definitions (right-side, left-side, range, increment, etc.) |
| Views | View Manager layouts, column configurations, preset sort sequences |
| Global File Configs | Miscellaneous application configuration settings |
| Store Groups | Named store number groupings and their members |
| Import Processing | POS import history records |
| Database Settings | Application settings (filtered -- see below) |
| Startup Checks | Startup validation toggle states |
| Database Connections | Known SQL Server connection entries |
What Does NOT Get Transferred
Certain settings are automatically excluded because they are machine-specific, security-sensitive, or track migration state:
| Category | Examples |
|---|---|
| License & Security | Software license key, admin password, encryption flags |
| Connection Strings | Database connection strings, FTP server addresses |
| Credentials | FTP usernames/passwords, MySQL credentials |
| Machine Paths | Local file paths, log file locations |
| Migration Flags | One-time migration markers, script execution history |
| Runtime State | Last sync dates, import timestamps, BCP statistics |
| Store Identity | Store number, store count (set during database creation) |
This filtering prevents the source database's machine-specific configuration from overwriting the current database's local settings.
