ERP migration
Field-level mapping, validation, and rollback between Alpha-E GSoft-POS and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Alpha-E GSoft-POS
Source
Dolibarr ERP
Destination
Compatibility
9 of 12
objects map 1:1 between Alpha-E GSoft-POS and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Alpha-E GSoft-POS to Dolibarr is a migration from a vertical-market on-premise POS-ERP built for Indian garment and footwear retail into a general-purpose open-source ERP-CRM. Alpha-E GSoft-POS has no public API, which means every extraction proceeds through direct database reads or manual exports from the vendor-assisted desktop application. We handle the extraction, data cleaning, and schema mapping across Dolibarr's modular architecture, where modules for Products, Third Parties, Invoicing, Stock, and Accounting must be activated and configured before any import begins. We preserve GSTIN-annotated invoice data for re-filing in the GST portal post-migration, consolidate multi-branch data from dispersed GSoft-POS tables into unified Dolibarr warehouse or project structures, and reconcile opening balances where fiscal year boundaries differ between systems. We do not migrate workflows, automations, or loyalty scheme logic as code; these require manual rebuild in Dolibarr using its built-in triggers and third-party add-ons.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Alpha-E GSoft-POS object lands in Dolibarr ERP, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Alpha-E GSoft-POS
Items
Dolibarr ERP
Products (llx_product)
1:1GSoft-POS Items with barcode, SKU, MRP, size/color variants, and HSN code map directly to Dolibarr Products. Variant attributes (size, color) map to Dolibarr's product_attribute configuration. Barcode values migrate into the barcode field. We extract every item record including its current stock quantity, reorder level, and min/max thresholds, and write them as Dolibarr product stock entries after the initial product insert. HSN codes from GSoft-POS map to the pcode上前 field or a custom product field if the Dolibarr installation lacks the Indian HSN module.
Alpha-E GSoft-POS
Customers
Dolibarr ERP
Third Parties - Customers (llx_societe)
1:1GSoft-POS Customer records (name, GSTIN, address, phone, email, outstanding balance, credit limit) map to Dolibarr Third Parties with the customer type flag set. GSTIN migrates to the siret or a custom field (tva_intra) depending on the Dolibarr tax module configuration. Outstanding balance and credit limit become Dolibarr receivable limit fields. Purchase history from GSoft-POS invoices is linked to the Third Party via Dolibarr commercial proposals and orders modules.
Alpha-E GSoft-POS
Vendors
Dolibarr ERP
Third Parties - Suppliers (llx_societe)
1:1GSoft-POS Vendor master (name, contact, GSTIN, payment terms, address) maps to Dolibarr Third Parties with the supplier type flag. Payment terms from GSoft-POS (e.g., Net 30) map to the Dolibarr cond_reglement code on the supplier record. We preserve the full vendor address and GST registration details for GST input tax credit reconciliation.
Alpha-E GSoft-POS
Sales Invoices
Dolibarr ERP
Invoices (llx_facture)
1:1GSoft-POS GST-compliant sales invoices migrate to Dolibarr Invoices as paid or unpaid records depending on the payment status in the source. Each invoice line (item, quantity, rate, tax rate, CGST/SGST/IGST breakup, discount) maps to Dolibarr invoice lines. We extract the GSTIN of both parties from GSoft-POS and store them as custom fields since Dolibarr's standard invoice does not have a native dual-GSTIN field. The invoice-to-payment linkage (receipt vouchers) is preserved by matching payment amounts and dates against receipt records.
Alpha-E GSoft-POS
Purchase Orders
Dolibarr ERP
Supplier Orders (llx_commande_fournisseur)
1:1GSoft-POS Purchase Orders with vendor, items ordered, quantities, rates, taxes, and pending/received status map to Dolibarr Supplier Orders. Pending quantities in GSoft-POS become open order lines in Dolibarr. Received quantities are reconciled against any incoming stock entries migrated separately. The vendor GSTIN is preserved on the supplier order for input tax tracking.
Alpha-E GSoft-POS
Receipt Vouchers / Payments
Dolibarr ERP
Payments (llx_paiement + llx_paiement_facture)
1:1GSoft-POS payment records (cash, bank, credit) linking to sales or purchase invoices map to Dolibarr Payment records. Each payment is linked to its corresponding invoice via the paiement_facture join table. Payment mode from GSoft-POS (cash, cheque, NEFT, RTGS, UPI) maps to the Dolibarr bank line code. We use invoice reference and amount as the dedupe key when linking payments to invoices during migration.
Alpha-E GSoft-POS
Chain Store Branches
Dolibarr ERP
Projects (llx_projet) + Warehouses
1:manyMulti-location GSoft-POS branch data is dispersed across branch-specific tables or shared tables with a branch_id discriminator. There is no single export in GSoft-POS; we write branch-specific extraction queries and consolidate them into a unified dataset. Each branch becomes a Dolibarr Project (for financial reporting and task management per location) and optionally a separate Warehouse (for stock segregation if Dolibarr's stock module is active). Branch-level sales and stock summaries migrate as historical project data entries.
Alpha-E GSoft-POS
Loyalty Members
Dolibarr ERP
Members (llx_adherent)
1:1GSoft-POS loyalty member records (member ID, points balance, tier, redemption history, contact details) map to Dolibarr Members module. Points balance migrates as a custom field on the Member record. Redemption history migrates as Member events or notes depending on the Dolibarr version. GSoft-POS loyalty rules (tier thresholds, earning rates, expiry policy) are not transferable as code; we document the rules for the customer's admin to re-implement in Dolibarr's third-party loyalty add-on or a custom field-based tier system.
Alpha-E GSoft-POS
Financial Ledgers
Dolibarr ERP
Accounting (llx_accounting_account + llx_accountrpt)
1:1GSoft-POS chart of accounts, ledger balances, and trial balance transfer to Dolibarr Accounting if the Accounting module is active. Opening balance dates and fiscal year closing conventions differ from Dolibarr's default fiscal year, so we compute the carry-forward amounts at the point of transition and insert them as opening balance entries in Dolibarr's accounting journal. We flag any accounts that reference GST tax codes (CGST input, SGST input, IGST payable) for manual verification against the Dolibarr tax configuration.
Alpha-E GSoft-POS
GST Reports (GSTR-1, GSTR-2, GSTR-3B)
Dolibarr ERP
Tax Records (re-filed post-migration)
lossyGST filings are India-specific transactional summaries generated in the GST portal. We extract all underlying invoice data that feeds GSTR-1, GSTR-2, and GSTR-3B (invoice numbers, dates, GSTIN, HSN, taxable value, tax amounts, place of supply) from GSoft-POS as structured CSV files organized by return period. The filing itself must be re-entered directly in the GST portal or through a GST reconciliation tool post-migration. We deliver a per-period invoice export that maps directly to the GST portal's upload format.
Alpha-E GSoft-POS
Stock / Inventory
Dolibarr ERP
Stock (llx_product_stock)
1:1GSoft-POS item stock levels (branch-wise and aggregate) map to Dolibarr Stock entries in the stock module. We extract current stock by item and by branch from the GSoft-POS inventory tables, then write stock movements as Dolibarr stock movement records. If GSoft-POS tracks min/max reorder levels, these migrate as Dolibarr product reordering rules. Stock valuation amounts from GSoft-POS reconcile against Dolibarr's warehouse stock report after import.
Alpha-E GSoft-POS
Opening Balances
Dolibarr ERP
Opening Entries (llx_accountrpt or journal entries)
lossyGSoft-POS stores opening balances as carry-forward entries at the start of each fiscal year. We extract the current fiscal year's opening balances for receivables, payables, and inventory, then write them as opening journal entries in Dolibarr's accounting module before any transaction import begins. This prevents double-counting of revenue or inventory when GSoft-POS's year-closing convention differs from Dolibarr's default April-March fiscal year.
| Alpha-E GSoft-POS | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Items | Products (llx_product)1:1 | Fully supported | |
| Customers | Third Parties - Customers (llx_societe)1:1 | Fully supported | |
| Vendors | Third Parties - Suppliers (llx_societe)1:1 | Fully supported | |
| Sales Invoices | Invoices (llx_facture)1:1 | Fully supported | |
| Purchase Orders | Supplier Orders (llx_commande_fournisseur)1:1 | Fully supported | |
| Receipt Vouchers / Payments | Payments (llx_paiement + llx_paiement_facture)1:1 | Mapping required | |
| Chain Store Branches | Projects (llx_projet) + Warehouses1:many | Mapping required | |
| Loyalty Members | Members (llx_adherent)1:1 | Mapping required | |
| Financial Ledgers | Accounting (llx_accounting_account + llx_accountrpt)1:1 | Mapping required | |
| GST Reports (GSTR-1, GSTR-2, GSTR-3B) | Tax Records (re-filed post-migration)lossy | Mapping required | |
| Stock / Inventory | Stock (llx_product_stock)1:1 | Fully supported | |
| Opening Balances | Opening Entries (llx_accountrpt or journal entries)lossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Alpha-E GSoft-POS gotchas
No documented public API for data export
GST data must be re-filed after migration
Historical data retention and fiscal year boundaries
Chain store branch data lacks a single export button
Dolibarr ERP gotchas
Foreign key constraint errors on cross-distribution database restore
SQL injection vulnerabilities in version 9.0.1
Custom fields stored as JSON in extraoptions require field-by-field deserialization
Decimal precision and rounding configuration affects price fields
No native iOS/Android app forces reliance on browser
Pair-specific challenges
Migration approach
Database access provisioning and discovery
We begin by confirming that the customer can provide a current backup of the GSoft-POS SQL database and read credentials for direct database access. We audit the database schema to identify tables for Items, Customers, Vendors, Invoices, Purchase Orders, Receipt Vouchers, Chain Store Branches, Financial Ledgers, Loyalty Members, and Stock. We document the fiscal year boundaries, branch table structure, and any custom fields in the database. If direct database access is unavailable, we scope extraction to what vendor-assisted manual exports can produce and flag reduced historical scope upfront.
Dolibarr module activation and configuration
We install and configure a clean Dolibarr instance (or work with the customer's existing Dolibarr installation) and activate only the modules required for the migration scope: Products/Services, Stock, Third Parties (Customers and Suppliers), Invoices, Supplier Orders, Payments, Projects, Members (for loyalty), and Accounting. We configure the India-specific tax rules for each applicable state and tax type before any data import. We also define the fiscal year, currency (INR), and default payment terms during this phase so that imported data is consistent from day one.
Data extraction and cleaning
We run branch-specific SQL extraction queries against the GSoft-POS database to pull all records in dependency order: Items first (no dependencies), then Customers and Vendors, then Invoices and Purchase Orders, then Payments and Receipt Vouchers, then Financial Ledgers, then Loyalty Members and Stock. We clean the extracted data: removing duplicate customer and item records, standardizing GSTIN formats (15-character format validation), correcting date formats to YYYY-MM-DD, and resolving any null values in required fields. We produce a data quality report before any import begins.
Sandbox migration and reconciliation
We run a full migration into a staging Dolibarr instance (a copy of the production installation) using production-like data volume. We verify that Items appear in the Dolibarr product catalog with correct barcode and variant attributes, that Customers and Vendors are searchable and linked to the correct type, that invoices carry correct line items and tax amounts, and that branch data appears under the correct Projects. The customer's finance lead spot-checks 25-50 records against the GSoft-POS source and signs off the mapping before production migration begins.
Production migration in dependency order
We run production migration in the same record-dependency sequence validated in staging: Products first, then Third Parties (Customers and Vendors), then Stock entries, then Invoices and Supplier Orders, then Payments linked to invoices, then Projects and Warehouses for branch consolidation, then Financial Ledger opening balances, and finally Loyalty Members. Each phase emits a row-count reconciliation report showing records inserted, updated, skipped, and errored. Errors are resolved before the next phase begins. We freeze GSoft-POS writes during the cutover window and run a final delta migration of any records modified during the migration window.
Cutover, GST data handoff, and admin documentation
We enable Dolibarr as the system of record and deliver the GST invoice export files organized by return period (GSTR-1, GSTR-2, GSTR-3B) for re-filing in the GST portal. We deliver a written document describing the loyalty scheme rules extracted from GSoft-POS, the Dolibarr module activation checklist, and the automation rebuild inventory for the customer's admin to re-implement in Dolibarr's trigger system or a third-party add-on. We support a three-day hypercare window for reconciliation issues raised by the customer's team.
Platform deep dives
Alpha-E GSoft-POS
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Alpha-E GSoft-POS and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Alpha-E GSoft-POS and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between Alpha-E GSoft-POS and Dolibarr ERP.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Alpha-E GSoft-POS: Not applicable — no public API surface is exposed..
Data volume sensitivity
Alpha-E GSoft-POS doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Alpha-E GSoft-POS to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Alpha-E GSoft-POS to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Alpha-E GSoft-POS
Other ways to arrive at Dolibarr ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.