The consultants had a problem. Myers-Holum helped other companies connect their business systems, yet its own sales, accounting and project work lived in three different applications. QuickBooks kept the books. Salesforce tracked opportunities. Mavenlink handled projects, time and expenses. The awkward part was deciding who could do the work being sold.
- Implements NetSuite and connects the systems around it.
- Customer work spans footwear, connected sports products and food banks.
- NS90 packages migration by how much business history you need.
A customer engagement needed the right combination of skills, availability and geography. But Myers-Holum could not allocate resources until after closing a sale. Information existed; assembling it was the chore. In early 2023, the firm replaced all three applications with NetSuite, launching CRM in January and completing the remaining ERP work in March. Its own business supplied a compact explanation of what it sells: fewer gaps between a decision and the information needed to make it.
The business between the boxes
Enterprise resource planning sounds distant from ordinary work. It becomes less mysterious when someone needs to know whether an order shipped, which subsidiary earned the money, or whether a consultant is available next Tuesday. Myers-Holum configures the financial and operational machinery behind those questions. Its work includes implementation, customization, data migration, commerce, payments and ongoing support.
Mark Myers and Knute Holum met in Price Waterhouse’s Management Advisory Services division before founding the firm in 1981. Its data and analytics practice followed in 2000. That background matters: an implementation can involve far more than installing an application. Old account structures, duplicated customer records and years of transactions have to make sense inside the new arrangement.
The company describes a team of more than 425 consultants, developers and specialists, serving smaller businesses through large enterprises. Its stated culture emphasizes stewardship, collaboration and continuous learning. Those are useful ambitions for people whose work requires finance, operations and technology teams to agree on what a transaction means.
Follow a pair of shoes
At footwear seller Orva, the trouble was the journey between systems. Separate merchandising and financial applications made a shared operating picture difficult. Marketplace connections were limited. Staff uploaded files, downloaded files and passed spreadsheets around. Growth meant more people tending the transfers.
Myers-Holum served as lead system integrator, coordinating electronic data interchange with more than 150 vendor partners. Purchase orders, shipment notices and invoices could travel electronically. Seven third-party warehouses also used electronic connections for orders and inventory movements. NetSuite became the core for purchasing, inventory, sales and finance.
“NetSuite is at the core of everything we do.”Lee Cappiello · Director of IT, Orva
Orva’s selection offers a clue to the firm’s positioning. The retailer considered multiple partners and valued Myers-Holum’s attention to training, change management and user acceptance testing alongside technical work. A functioning connection has to survive contact with the people using it. An elegant diagram cannot teach a warehouse team a new routine.
A bat with a subscription attached
Diamond Kinetics brought a different puzzle. Its baseball and softball technology combined physical products with software subscriptions. Payments and subscriptions across platforms needed reconciliation, while its previous commerce setup was poorly suited to the bundle. Accounting for both hardware and software added another complication.
Myers-Holum helped connect Stripe to NetSuite, set up accounting and support a BigCommerce storefront that could sell the combination. Here the useful unit of work was a customer purchase extending across several applications. The team had to preserve the relationship between the product, the subscription and the accounting record.
Stripe named Myers-Holum its 2022 North America Partner of the Year, announced in April 2023. NetSuite, Google Cloud, Boomi and Celigo also sit in its partner ecosystem. The firm occupies the implementation layer: it makes those platforms work for particular businesses.
How much history comes along?
NS90 turns part of that work into a packaged offering. Migrate extracts legacy ERP data, maps accounts, cleans records and validates the result. The marketed methodology offers a proof of concept in 45 days and go-live in 90. That is a migration proposition whose scope needs agreement before the clock becomes meaningful.
Keep the trail from the old account to the new number.
The surrounding offerings handle connections, analytics and monitoring. ACE, the Account Classification Engine, aggregates high-volume transaction data into accounting entries while retaining lineage to the detail. Integrate connects external systems through an Oracle-cloud data hub. Manage adds monitoring and reconciliation. These address the work that continues after migration day.
The published migration tiers start at $9,000 for trial balances, $12,000 with drill-down to source transactions, $24,000 including master data and open transactions, and $42,000 for full historical transactions. Those are starting prices for defined scopes. NS90 Integrate separately lists Starter implementation at $9,000 plus a $9,000 annual subscription.
Start with the handoff
Buyers can also consider specialist partners such as Bryant Park Consulting, which offers NetSuite implementation, integrations and analytics. Myers-Holum’s case rests on its data-management background, packaged tools and documented customer work. Choosing among firms still requires checking the proposed team, relevant references and scope.
The practical lesson is to map a transaction before buying another application. Identify where someone rekeys it, reconciles it or waits for it. Decide which historical records must remain available. Give the people responsible for the books a concrete validation task.
A migration schedule depends on those decisions. Unsupported source systems and custom requirements need separate scoping; unresolved account definitions will not disappear during a transfer. For a small business with simple needs, the work may not justify the expense. For a company spending its days ferrying information between otherwise capable systems, the handoff is a sensible place to begin.