[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-legacy-data-migration-en":3,"blog-adjacent-legacy-data-migration-en":29,"blog-related-legacy-data-migration-en":65},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":28},39,"legacy-data-migration","Data Migration: Understand the Old Ledger First","Migrations rarely fail on technology. They fail because nobody can describe what the legacy data actually contains.","\u003Cp>In replacement projects, data migration is usually scheduled last and estimated most optimistically. Across several migrations, the lesson is consistent: the time goes into understanding legacy history, not into writing scripts.\u003C\u002Fp>\n\u003Ch2>Three tables before migration\u003C\u002Fh2>\n\u003Cp>A field mapping table from old to new, including type conversion and null handling.\u003C\u002Fp>\n\u003Cp>A data quality table counting missing, duplicated and malformed values, which yields a cleaning estimate.\u003C\u002Fp>\n\u003Cp>A business sign-off table listing what must be kept and what can be archived, signed by the business owner.\u003C\u002Fp>\n\u003Ch2>Execution strategy\u003C\u002Fh2>\n\u003Cp>Build the full script, then run it three times on a test database: once for errors, once for row counts, once for financial fields.\u003C\u002Fp>\n\u003Cp>Rehearse a switchover including rollback; on launch day only sync the delta to keep downtime short.\u003C\u002Fp>\n\u003Cp>Keep the old database read-only for three months so the business can still look up history.\u003C\u002Fp>\n\u003Cp>Migration is about keeping old data trustworthy in a new system. One number that does not reconcile erodes confidence in everything.\u003C\u002Fp>","","slate","佳益方圆团队","2026-07-01T10:57:00+08:00",1,false,[16,17,18],"Migration","Legacy","Delivery",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},0,"engineering","Engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","cpu","blue","article",60,{},{"previous":30,"next":48},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},18,"product-or-project-shop","Product Company or Project Shop?","Every project-driven team asks this. Our answer is not either\u002For, but which capabilities repeat often enough to reuse.","indigo","2026-07-03T09:44:00+08:00",[38,39,40],"Startup","Product","Strategy",{"id":42,"parentId":20,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":25,"kind":26,"sortOrder":47,"count":20},6,"founder-notes","Founder Notes","Reflections from the founding team on business, management and product, documenting the growth of a software company.","pen-tool",10,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},59,"ai-feature-positioning","Positioning an AI Feature","Treating a large model as a universal assistant usually produces features nobody uses. Start from a specific task.","2026-06-29T10:57:00+08:00",[55,56,57],"AI","Positioning","Adoption",{"id":59,"parentId":20,"slug":60,"name":61,"description":62,"icon":63,"cover":9,"tone":25,"kind":26,"sortOrder":64,"count":20},2,"product-thinking","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb",50,[66,77,88],{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":71,"author":11,"publishedAt":72,"updatedAt":72,"readingMinutes":13,"featured":14,"tags":73,"category":76},30,"integration-api-pitfalls","Five Traps in Enterprise System Integration","However complete the API documentation is, integration usually stalls on field semantics, timeouts and repeated pushes.","cyan","2026-10-17T09:00:00+08:00",[74,75,22],"Integration","APIs",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"id":13,"slug":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":71,"author":11,"publishedAt":81,"updatedAt":82,"readingMinutes":59,"featured":83,"tags":84,"category":87},"why-enterprise-systems-age","Why Enterprise Systems Start to Age After Three Years","A system can pass acceptance with every feature checked, then feel awkward three years later. The problem is rarely the code — it is the changes that were never considered at delivery.","2026-10-16T09:30:00+08:00","2026-10-18T15:58:14.648+08:00",true,[85,86],"System Evolution","Architecture",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"id":89,"slug":90,"title":91,"excerpt":92,"content":9,"cover":9,"tone":25,"author":11,"publishedAt":93,"updatedAt":93,"readingMinutes":13,"featured":14,"tags":94,"category":98},31,"idempotent-design-basics","Idempotency: Duplicate Submissions Are Not Just Double Clicks","Retries, redelivery and impatient users all send the same request more than once. Idempotency belongs in the API design.","2026-10-05T10:13:00+08:00",[95,96,97],"API Design","Idempotency","Reliability",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20}]