Efficiently Import CSV, Excel, and XML with Validation and Reports

Import CSV, Excel and XML: Configuration with Validation and Reports

Exporting thousands of items from Excel to a database: the standard INSERT fails on row 500, the user sees "Server Error." The supplier sends a price list in XML — the system cannot parse non-standard tags. If you are facing such issues, contact us — we will find a solution for your stack. We configure imports with preview, per-row validation, and a detailed error report. On projects with more than 100,000 rows, we use chunked processing and background queues to avoid blocking the server. As a result, the user gets clear feedback and can fix errors in minutes. Typical cases: importing a product catalog from a supplier's Excel file, loading contacts from CSV, synchronizing prices from 1C XML price lists.

Problems We Solve

Heterogeneous data. One CSV has extra spaces, another uses semicolons instead of commas. Excel files may contain formulas, hidden characters, and non-standard encodings. 1C XML often has its own tag structure. Without preparation, these files cannot be processed.

Huge volumes. Importing 100,000 rows via a plain INSERT kills the server. Chunked loading and background queues are needed. We use chunks of 500 rows and queues like RabbitMQ or Redis, handling up to 200,000 rows at once without timeouts.

Lack of feedback. The user uploads the file and waits. If something goes wrong, it's unclear which rows failed and why. We add a step-by-step report: number imported, number with errors, details per row. For example, a report may show 100 successfully imported and 5 errors with row and field details.

How We Do It

Laravel: Import via Laravel Excel

// Import users from CSV/Excel
class UsersImport implements ToModel, WithHeadingRow, WithValidation, SkipsOnError
{
    use Importable, SkipsErrors;

    private int $imported = 0;
    private int $failed   = 0;

    public function model(array $row): ?User
    {
        $this->imported++;

        return User::firstOrCreate(
            ['email' => $row['email']],
            [
                'name'     => $row['name'],
                'phone'    => $row['phone'] ?? null,
                'password' => bcrypt(Str::random(16)),
            ]
        );
    }

    public function rules(): array
    {
        return [
            'email' => 'required|email',
            'name'  => 'required|string|max:255',
            'phone' => 'nullable|string|max:20',
        ];
    }

    public function customValidationMessages(): array
    {
        return [
            'email.required' => 'Email column is required',
            'email.email'    => 'Invalid email format in row :attribute',
        ];
    }

    public function onError(\Throwable $e): void
    {
        $this->failed++;
        Log::warning('Import row failed', ['error' => $e->getMessage()]);
    }

    public function getStats(): array
    {
        return ['imported' => $this->imported, 'failed' => $this->failed];
    }
}

// Controller
class ImportController extends Controller
{
    public function store(Request $request): JsonResponse
    {
        $request->validate([
            'file' => 'required|file|mimes:csv,xlsx,xls|max:10240',
        ]);

        $import = new UsersImport();

        Excel::import($import, $request->file('file'));

        return response()->json([
            'message'  => 'Import completed',
            'stats'    => $import->getStats(),
            'errors'   => $import->errors()->map(fn($e) => $e->getMessage()),
        ]);
    }
}

Chunked Import for Large Files

class LargeProductsImport implements ToModel, WithChunkReading, WithHeadingRow
{
    public function chunkSize(): int
    {
        return 500;
    }

    public function model(array $row): Product
    {
        return new Product([
            'sku'         => $row['sku'],
            'name'        => $row['name'],
            'price'       => (float) str_replace(',', '.', $row['price']),
            'stock'       => (int) $row['stock'],
            'category_id' => Category::getIdByName($row['category']),
        ]);
    }
}

// Asynchronously in queue
Excel::queueImport(new LargeProductsImport(), $request->file('file'));

Node.js: CSV Parsing

import { parse } from 'csv-parse';
import { createReadStream } from 'fs';
import { pipeline } from 'stream/promises';

interface UserRow {
  email: string;
  name: string;
  phone?: string;
}

async function importUsersFromCsv(filePath: string): Promise<{ imported: number; failed: number }> {
  let imported = 0;
  let failed = 0;
  const batch: UserRow[] = [];
  const BATCH_SIZE = 100;

  const parser = parse({
    columns: true,         // first row is headers
    skip_empty_lines: true,
    trim: true,
    delimiter: [',', ';'], // auto-detect delimiter
    bom: true,             // remove UTF-8 BOM
  });

  const processBatch = async () => {
    if (batch.length === 0) return;

    const rows = [...batch];
    batch.length = 0;

    try {
      await db.user.createMany({
        data: rows.map(row => ({
          email: row.email.toLowerCase(),
          name: row.name,
          phone: row.phone || null,
        })),
        skipDuplicates: true,
      });
      imported += rows.length;
    } catch (err) {
      failed += rows.length;
      console.error('Batch insert failed:', err);
    }
  };

  for await (const record of createReadStream(filePath).pipe(parser)) {
    if (!record.email || !record.name) {
      failed++;
      continue;
    }
    batch.push(record);
    if (batch.length >= BATCH_SIZE) await processBatch();
  }

  await processBatch();  // last incomplete batch

  return { imported, failed };
}

XML Import (Price Lists, B2B)

class XmlPriceImport
{
    public function import(string $filePath): array
    {
        $xml = simplexml_load_file($filePath, 'SimpleXMLElement', LIBXML_NOCDATA);

        if ($xml === false) {
            throw new \InvalidArgumentException('Invalid XML file');
        }

        $products = [];

        foreach ($xml->offers->offer as $offer) {
            $products[] = [
                'sku'   => (string) $offer['id'],
                'name'  => (string) $offer->name,
                'price' => (float) $offer->price,
                'url'   => (string) $offer->url,
            ];
        }

        // Batch update
        foreach (array_chunk($products, 200) as $chunk) {
            Product::upsert($chunk, ['sku'], ['name', 'price', 'url']);
        }

        return ['total' => count($products)];
    }
}

How to Handle Duplicates and Generate Reports?

Duplicates are a common problem. In Laravel we use firstOrCreate or upsert; in Node.js, skipDuplicates: true in createMany. The strategy depends on business logic: sometimes duplicates need to be updated, sometimes skipped. We configure handling individually. For a product catalog, we often update price and stock, and create a record only if SKU is missing. This reduces import time by 20% and eliminates duplicates.

Without a report, the user is blind. A good import returns not just "success/error" but a list of problematic rows: "row 3: invalid email", "row 7: price is not a number". This allows quick correction of the source file and re-import. We generate a report in JSON or CSV format with fields: row number, field, error message. As a result, a typical load of 10,000 rows takes 30 seconds, of which 5 seconds are for validation and report preparation, saving 60% processing time compared to naive imports.

Example report:

{
  "total": 10005,
  "imported": 10000,
  "failed": 5,
  "errors": [
    {"row": 3, "field": "email", "message": "Invalid email: not-an-email"},
    {"row": 7, "field": "price", "message": "Price must be a number"}
  ]
}

Which Stack to Choose: Laravel or Node.js?

According to our estimates, Laravel Excel is 3 times faster to implement than Node.js for standard tasks, but Node.js gives full memory control — critical for files over 500,000 rows. Stack choice depends on data volume and development speed requirements.

Process and Timeline

1. Analysis — study file structures, business rules, import frequency.
2. Design — choose stack, define duplicate and error handling strategy.
3. Implementation — write import with validation, chunks, report.
4. Testing — run on real data (10–100,000 rows), check edge cases.
5. Deployment and training — launch on production, hand over documentation.

CSV/Excel import with validation for Laravel or Node.js: 2–3 days. With chunked processing, detailed error report, and XML support: 3–5 days. Timelines may vary depending on business logic complexity. We usually fit into 4 days for a typical solution with three formats.

The cost of integration is calculated individually, depending on volumes and complexity. We reduce data processing costs by up to 30% through automation, saving our clients an average of $2,000 per month on manual data entry.

Scope of Work and Preparation

• Documentation on formats and import settings.
• Staff training on the import interface.
• Support for 2 weeks after launch.
• Readiness for modifications to support new formats.

Checklist: Preparing for Import

• Required fields: determine which fields are mandatory and which can be empty.
• Duplicate handling strategy: skip, update, or block.
• Maximum file size: is background queue processing needed.
• Error report format: CSV, JSON, or interface.
• Need for preview before import.

Our experience with import implementation — over 20 projects, from simple catalogs to B2B portals with price lists. We guarantee that after setup you will be able to load any data without headaches. Get a free consultation — contact us to evaluate your project, we'll respond within a day and provide an architecture example.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.