Migrate your Info.Net data
ERP platform for SMB manufacturers built by LAMAR Software, offering end-to-end operational visibility with real-time reporting across inventory, orders, production scheduling, and quality control.
In its favor
Why people choose Info.Net
The signal that keeps Info.Net on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Real-time visibility across inventory, orders, production scheduling, and quality control in a single manufacturing ERP, reducing the need for spreadsheet-based reporting between departments.
Modern, intuitive interface that allows non-technical staff to build reports, dashboards, and set alerts without extensive training or developer support.
Cloud-based modular design that scales as manufacturing operations grow in size and complexity without requiring hardware investments.
Native mobile apps for iOS and Android let shop-floor employees check inventory levels and order status on-the-go without requiring desktop access.
24/7 customer support via phone, email, and ticketing gives smaller manufacturers access to assistance outside standard business hours.
Setup complexity and legacy system integration requires significant IT time and budget, especially for manufacturers with fragmented or older source systems.
Monthly subscription plus annual support fees accumulate to a significant cost burden for very small manufacturers with thin margins.
Workflow customization is limited and modifications beyond base configurations are difficult to implement, frustrating teams with unique manufacturing processes.
Reasons to switch
Why people leave Info.Net
The recurring reasons buyers give for replacing Info.Net. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Info.Net fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Info.Net pricing overview
Info.Net pricing is not publicly disclosed in available research. The platform is positioned for SMB manufacturers and operates on a monthly subscription model with annual support fees. Custom pricing is typical for deployments requiring multiple modules or enterprise-level capacity.
Custom (sales-led, Info.Net by LAMAR Software)
Tier 1 of 1
Not publicly published
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Info.Net's schedule — see our quote-based pricing →
What gets migrated
Info.Net object support
Object-by-object support for Info.Net migrations. Per-pair details surface during scoping.
Items
Fully supportedItems represent finished goods, raw materials, and components tracked in inventory. The schema is stable with standard fields for SKU, description, unit of measure, and cost. We migrate Items 1:1 with all associated pricing and BOM links preserved.
Production Orders
Fully supportedProduction Orders track manufacturing jobs with status, quantity, scheduled dates, and assigned work centers. We preserve the full production history including completion dates and scrap quantities.
Bill of Materials
Fully supportedBOMs define the component hierarchy for manufactured items. We map multi-level BOM structures, preserve revision versions, and link them correctly to their parent Items.
Quality Control Records
Mapping requiredQC logs hold inspection results, pass/fail flags, and measurement data linked to production lots. Field naming conventions vary between ERP systems; we map measurement field names and preserve linked lot identifiers.
Work Orders
Fully supportedWork Orders assign production tasks to employees or work centers with start/end dates and labor estimates. We migrate the full work order lifecycle including status transitions and actual labor consumed.
Vendors
Mapping requiredVendor master records include contact details, payment terms, and lead times. Address structures and multi-contact handling differ between ERPs; we apply field-level mapping and deduplicate duplicate vendor names.
Customers
Mapping requiredCustomer records hold billing addresses, shipping addresses, and credit limits. Multi-address customer accounts require special handling to ensure ship-to and bill-to are assigned correctly in the destination system.
Inventory Transactions
Fully supportedInventory movements (receipts, issues, adjustments, and transfers) carry timestamps, quantities, and locations. We preserve the full transaction ledger with post dates to maintain accurate stock valuations.
Custom Fields
Mapping requiredInfo.Net supports custom fields on Items, Customers, and Vendors. We extract custom field definitions, map their values to destination equivalents, and flag any custom fields with no matching target as candidates for post-migration cleanup.
User Accounts
Mapping requiredUser accounts carry role assignments and permission sets. We map roles to equivalent destination roles but cannot preserve individual password hashes; users will require password resets post-migration.
| Object | Support | Notes |
|---|---|---|
| Items | Fully supported | Items represent finished goods, raw materials, and components tracked in inventory. The schema is stable with standard fields for SKU, description, unit of measure, and cost. We migrate Items 1:1 with all associated pricing and BOM links preserved. |
| Production Orders | Fully supported | Production Orders track manufacturing jobs with status, quantity, scheduled dates, and assigned work centers. We preserve the full production history including completion dates and scrap quantities. |
| Bill of Materials | Fully supported | BOMs define the component hierarchy for manufactured items. We map multi-level BOM structures, preserve revision versions, and link them correctly to their parent Items. |
| Quality Control Records | Mapping required | QC logs hold inspection results, pass/fail flags, and measurement data linked to production lots. Field naming conventions vary between ERP systems; we map measurement field names and preserve linked lot identifiers. |
| Work Orders | Fully supported | Work Orders assign production tasks to employees or work centers with start/end dates and labor estimates. We migrate the full work order lifecycle including status transitions and actual labor consumed. |
| Vendors | Mapping required | Vendor master records include contact details, payment terms, and lead times. Address structures and multi-contact handling differ between ERPs; we apply field-level mapping and deduplicate duplicate vendor names. |
| Customers | Mapping required | Customer records hold billing addresses, shipping addresses, and credit limits. Multi-address customer accounts require special handling to ensure ship-to and bill-to are assigned correctly in the destination system. |
| Inventory Transactions | Fully supported | Inventory movements (receipts, issues, adjustments, and transfers) carry timestamps, quantities, and locations. We preserve the full transaction ledger with post dates to maintain accurate stock valuations. |
| Custom Fields | Mapping required | Info.Net supports custom fields on Items, Customers, and Vendors. We extract custom field definitions, map their values to destination equivalents, and flag any custom fields with no matching target as candidates for post-migration cleanup. |
| User Accounts | Mapping required | User accounts carry role assignments and permission sets. We map roles to equivalent destination roles but cannot preserve individual password hashes; users will require password resets post-migration. |
Gotchas
What to watch for in Info.Net migrations
Issues we've hit on past Info.Net migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Initial setup and legacy migration require IT resources
Ongoing subscription and support costs are significant for very small manufacturers
Customization beyond base workflows is limited
No publicly documented API in available research
| Severity | Issue |
|---|---|
| High | Initial setup and legacy migration require IT resources |
| Medium | Ongoing subscription and support costs are significant for very small manufacturers |
| Medium | Customization beyond base workflows is limited |
| High | No publicly documented API in available research |
Leaving Info.Net?
Where Info.Net customers move next
6 destinations Info.Net can migrate to.
How a Info.Net migration works
Four steps, Info.Net-specific
Connect
Not publicly documented. into Info.Net. Scopes limited to read-only on the data we move.
Map
We translate Info.Net-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Info.Net quirks before production.
Migrate
Full migration with Info.Net rate-limit handling. Rollback available throughout.
FAQ
Info.Net migration FAQ
Answers to the questions buyers ask most during Info.Net migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Info.Net migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Info.Net.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Info.Net setup and destination — written quote back within a business day.