Identify what exists in an older Mamut integration and plan a controlled switch without starting a new, uncontrolled sync.
This guide is for existing Swedish Mamut users and their administrators/integrators. It is historical guidance, not a recommendation to reinstall a supported Mamut product. A current Abicart package does not make a discontinued vendor product supported.
1. Read the discontinuation notice
According to Visma's announcement about Mamut in Sweden maintenance/support ended on December 31, 2024. Registration of new data in the system was closed on August 1, 2025, when the license/support agreements were terminated. Any access to existing data is not the same as ongoing vendor support.
Older system requirement lists, Windows installation programs, and integration materials do not prove a currently supported product pair. Do not run an old installation archive as a first step.
2. Understand the historical connection
The older Windows application between Textalk Webshop/Abicart and Mamut could:
retrieve new customers and transfer them to Mamut,
retrieve new orders and transfer them to Mamut,
transfer inventory and prices from Mamut to the store,
transfer product registers in both directions and an existing customer register to the store.
A record being retrieved by the integration program is not the same as it being transferred to or posted in Mamut. Check where the data actually is before making migration selections or retrying.
3. Take inventory before changing anything
Identify the correct store/sub-store, Mamut company database, and any local integration installation.
Document the last known retrieval/transfer and where remaining orders, customer cards, and products are located.
Map out product/variant numbers, customer numbers, order number series, and any prefixes so that a new system does not create collisions.
Document fee products for shipping, payment fees, and discounts, as well as relevant currency/VAT connections.
Determine which source contains the correct prices, inventory, products, and customers for the migration.
Secure approved backups/exports and necessary archival records according to the company's legal requirements. Do not put passwords or customer exports in an open planning document.
4. Plan the new integration path
When switching systems, one person needs to be responsible for ensuring that the last transferred orders and customer/product changes are reconciled in both systems. Pause old scheduled transfers in the integration program before a new connection starts writing. Do not restart old transfers to fill a gap without first checking what has already been transferred. Preserve the old database and archival material; a paused sync is not a deletion.
Choose a currently supported accounting system and check its integration access, company, data mapping, and Abicart's package/add-on terms. Pro has an included ERP choice, but it is not a promise of unlimited connections or vendor licenses.
Plan a limited, permitted migration test and verify the correct quantities, numbers, balances, prices, and document references in the destination system before a larger transfer. A discontinued integration should not be subjected to a new resync to try to prove it is free of duplicates. Also document how old orders and archival data can be tracked without creating new accounting events.
Quick start
Assume that Mamut is a discontinued Swedish product.
Take inventory of the existing database, store, and transfer statuses.
Secure data and map out numbers, fees, and data sources.
Choose a current integration path and check the migration result before a major switch.
Subscription and access
This guide is for historical Mamut data. A new Abicart package does not restore the provider's discontinued support or license. A replacement integration has its own package, agreement, and permission requirements.
