从Magento 1切换至Magento 2的每日第三方数据导入方案咨询

Hey Stef, great question—making the jump from Magento 1's Magmi to Magento 2 means reworking your import workflow, since Magmi doesn’t support M2. Let’s break down your two main options, plus how to align them with your existing M2E Amazon/eBay setup:

Option 1: Magmi-like Third-Party Tools (No-Code/Low-Code) #

If you want a drop-in replacement for Magmi’s ease of use and daily scheduling, these tools are your best bet—most are built to handle CSV imports seamlessly and play nice with M2E:

• Firebear Import Export Pro
  This is the closest you’ll get to Magmi for M2. It supports visual CSV field mapping, scheduled daily imports (via cron), incremental updates (so you don’t re-import everything every day), and robust error handling. Crucially, it has built-in compatibility with M2E: you can exclude M2E-specific fields (like listing IDs or synced inventory values) from being overwritten, ensuring your Amazon/eBay sync stays intact.
• Aitoc Import/Export Toolkit
  Another solid choice with scheduled import capabilities. It lets you map custom CSV fields to Magento 2 attributes and includes safeguards for M2E data—you can set rules to skip fields that are managed by M2E (e.g., price if it’s synced from Amazon) to avoid conflicts.
• Magento 2 Native Import + Cron
  If budget is tight, the native import tool works with cron jobs for daily runs, but it’s less flexible than Magmi. You’ll need to ensure your CSV strictly follows Magento 2’s format rules, and incremental imports require manual filtering (e.g., only importing rows with a modified date). For M2E, make sure to exclude fields tied to M2E listings (check your database’s m2e_pro_product table for reference) to prevent breaking syncs.

Option 2: Custom PHP Interface (Using Magento 2 Native Classes) #

If your CSV has unique formatting, you need complex business logic (like data cleaning or internal system integrations), or you want full control over the import process, building a custom solution makes sense:

• Core Classes to Use
  Leverage Magento 2’s native import classes, like \Magento\CatalogImportExport\Model\Import\Product for product imports. You can write a standalone PHP script that loads your CSV, processes the data (e.g., validate SKUs, clean values), and triggers the import. Schedule this script via cron for daily runs.
• M2E Integration Tips
  When building your custom tool, add checks to avoid overwriting M2E-managed data:
  • Query the m2e_pro_product table to identify products linked to Amazon/eBay listings.
  • Skip fields that are synced via M2E (e.g., qty if inventory is managed from Amazon, or price if it’s synced from eBay).
  • Use M2E’s internal hooks to refresh listings after import if needed.
• Pros & Cons
  The upside is full customization to fit your exact needs; the downside is ongoing maintenance—you’ll need to update the script when Magento 2 releases new versions, and debug any integration issues with M2E.

Final Recommendation #

If your daily imports are straightforward (standard CSV format, no complex logic), go with a third-party tool like Firebear—it’s fast to set up, handles scheduling out of the box, and avoids M2E conflicts. If you have unique requirements that off-the-shelf tools can’t meet, build a custom interface using Magento 2’s native classes, but make sure to prioritize M2E data protection in your code.

内容的提问来源于stack exchange，提问作者Ste